[
https://jira.codehaus.org/browse/SUREFIRE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329598#comment-329598
]
Andreas Dolk commented on SUREFIRE-1019:
----------------------------------------
I already tried different executions, but that didn't work, because I can't
pull the dependencies to set the providers *into* the executions. If I could,
that would solve my problem immediately.
They're outside with the unwanted effect, that *both* providers try to handle
all executions - plus the undeclared "default-tests", which triples the build
time and causes build fails in case one provider doesn't find executable tests
in one execution.
As I said, I'm pretty lost...
> TestNG provider fails to execute JUnit4 tests
> ---------------------------------------------
>
> Key: SUREFIRE-1019
> URL: https://jira.codehaus.org/browse/SUREFIRE-1019
> Project: Maven Surefire
> Issue Type: Bug
> Components: TestNG support
> Affects Versions: 2.15
> Reporter: Andreas Dolk
> Assignee: Andreas Gudian
> Fix For: 2.16
>
> Attachments: maven-log.txt
>
>
> TestNG won't run certain jUnit tests. The test that showed this behaviour are
> compiled from specs bei jnario and use the special jnario test runner. During
> a maven build, TestNG "inspects" all test classes but doesn't execute any
> test method.
> This thread on the maven uses mailing list contain further informations about
> this issue:
> http://mail-archives.apache.org/mod_mbox/maven-users/201307.mbox/%3ccakbglvvdaw7tibdyxpjqnnwgknmkxecwdre_m5ncbh6u06v...@mail.gmail.com%3E
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
