You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2015/07/17 01:23:04 UTC

[jira] [Commented] (SUREFIRE-1168) failsafe won't exclude scope 'provided'

    [ https://issues.apache.org/jira/browse/SUREFIRE-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630508#comment-14630508 ] 

Tibor Digana commented on SUREFIRE-1168:
----------------------------------------

See the documentation because the values are different for this parameter.
The effect you want does not have solution and you should exclude the artifact explicitely via classpathDependencyExcludes.

> failsafe won't exclude scope 'provided'
> ---------------------------------------
>
>                 Key: SUREFIRE-1168
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1168
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Failsafe Plugin
>    Affects Versions: 2.18.1
>            Reporter: Benson Margulies
>
> https://github.com/bimargulies/failsafe-cp-tc is a test case.
> I have a jar with provided scope which needs to _not_ be in the classpath when running the tests. So, I wrote:
> {code}
>             <configuration>
>                 <classpathDependencyScopeExclude>provided</classpathDependencyScopeExclude>
>             </configuration>
> {code}
> No such luck, the jar remains in the classpath. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)