maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (SUREFIRE-370) Make testing frameworks artifact names configurable in plugin
Date Mon, 12 Nov 2007 20:51:25 GMT

     [ http://jira.codehaus.org/browse/SUREFIRE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter updated SUREFIRE-370:
----------------------------------

    Fix Version/s: 2.4

> 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: Critical
>             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

        

Mime
View raw message