[
http://jira.codehaus.org/browse/SUREFIRE-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232600#action_232600
]
Larry Shatzer commented on SUREFIRE-615:
----------------------------------------
In my company we have junit excluded from testng, to avoid having developers
use JUnit in favor of TestNG, as the standard (Not saying that is the best, but
the way they wanted things here).
Upgrading to Surefire 2.6 causes that same error (the NoClassDefFoundError).
I've had to downgrade back to 2.5.
What are my best options?
> Surefire providers shouldn't need to download old versions of the library
> -------------------------------------------------------------------------
>
> Key: SUREFIRE-615
> URL: http://jira.codehaus.org/browse/SUREFIRE-615
> Project: Maven Surefire
> Issue Type: Improvement
> Components: JUnit 3.x support, Junit 4.x support, Maven Surefire
> Plugin, TestNG support
> Affects Versions: 2.5
> Reporter: Brett Porter
> Assignee: Stephen Connolly
> Fix For: 2.6
>
>
> currently, the Surefire plugin uses resolveTransitively to obtain the
> Surefire provider (junit, junit4, junit47, testng). Each of these has a
> compile time dependency on the library itself to interact with their API.
> This results in downloading older versions as well as the newer one requested
> by the project (TestNG 5.7, JUnit 4.0, JUnit 3.8.1). There are two possible
> solutions to this:
> - alter the resolveTranstively method to exclude the artifact that is already
> available from the project
> - set the dependency to 'provided' in the providers POM
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
