[
http://jira.codehaus.org/browse/SUREFIRE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221915#action_221915
]
A edited comment on SUREFIRE-576 at 5/20/10 8:14 AM:
-----------------------------------------------------
Actually I see the issue better now. For scope ExcludesArtifactFilter is used
and for individual artifacts ExcludesArtifactFilter is used so it seems either
a new method needs to be created or ExcludesArtifactFilter changed to
IncludesArtifactFilter and filterArtifacts() to reflect that.
For the second issue with scope names I tried using maven 2.2.1 but still I
can't make a system artifact to be excluded.
was (Author: avalon):
Actually I see the issue better now. For scope ExcludesArtifactFilter is
used and for individual artifacts ExcludesArtifactFilter is used so it seems
either a new method needs to be created or ExcludesArtifactFilter changed to
IncludesArtifactFilter and filterArtifacts() to reflect that.
> 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, Maven Surefire Plugin
> Reporter: Hardy Ferentschik
> Assignee: Paul Gier
> Fix For: 2.6
>
>
--
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
