[
https://issues.apache.org/jira/browse/SUREFIRE-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630627#comment-14630627
]
Benson Margulies commented on SUREFIRE-1168:
--------------------------------------------
I did read the doc, quoted below. It mentions provided. Further, it references
a class, and that class contains
org.apache.maven.artifact.Artifact#SCOPE_PROVIDED. So I continue to see this as
a bug.
{noformat}
A dependency scope to exclude from the test classpath. The scope should be one
of the scopes defined by org.apache.maven.artifact.Artifact. This includes the
following:
compile - system, provided, compile
runtime - compile, runtime
compile+runtime - system, provided, compile, runtime
runtime+system - system, compile, runtime
test - system, provided, compile, runtime, test
{noformat}
> 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)
