[
http://jira.codehaus.org/browse/SUREFIRE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Fabulich closed SUREFIRE-370.
---------------------------------
Resolution: Duplicate
Duplicate of SUREFIRE-352. That bug gives a slightly better justification for
this improvement (and also includes a patch)
> Make testing frameworks artifact names configurable in plugin
> -------------------------------------------------------------
>
> Key: SUREFIRE-370
> URL: http://jira.codehaus.org/browse/SUREFIRE-370
> Project: Maven Surefire
> Issue Type: Improvement
> Components: plugin
> Affects Versions: 2.3
> Reporter: Mauro Talevi
> Assignee: Mauro Talevi
> Priority: Minor
> Fix For: 2.4
>
>
> The artifact names of the testing frameworks are hard-coded - junit:junit and
> org.testng:testng.
> We should make them configurable - due to the possibility that the names may
> change.
> Following use case demostrates the point: as of JUnit 4.4 - there are *two(
> junit artifacts, junit:junit and junit:junit-dep, with and without hamcrest
> jar bundled. Using only junit-dep will cause a NPE.
> Two simple configuration properties - junitArtifactName and
> testngArtifactName - which default to junit:junit and org.testng:testng will
> be sufficient and completely backward compatible.
--
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
