You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hardy Ferentschik (JIRA)" <ji...@codehaus.org> on 2009/10/08 18:10:43 UTC

[jira] Commented: (SUREFIRE-576) Have the abiltiy to remove a dependency from the test classpath (at least optional ones

    [ http://jira.codehaus.org/browse/SUREFIRE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194059#action_194059 ] 

Hardy Ferentschik commented on SUREFIRE-576:
--------------------------------------------

Forgot to describe a usecase. Say you are developing a library and you have an optional dependency to another library. Depending on whether this optional library is used at runtime your own library behaves differently. In this scenario I would like to have two test sets. One where the tests are run with the optional dependency on the classpath and one without. It is already possible two configure two executions of the surefire plugin, but I cannot remove a dependency. Basically optional dependencies should be removable via some excludes configuration. 

> Have the abiltiy to remove a dependency from the test classpath (at least optional ones
> ---------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-576
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-576
>             Project: Maven Surefire
>          Issue Type: New Feature
>          Components: classloading
>            Reporter: Hardy Ferentschik
>


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