[
https://issues.apache.org/jira/browse/SUREFIRE-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631313#comment-14631313
]
Tibor Digana commented on SUREFIRE-1168:
----------------------------------------
I think the surefire did not properly clarify "life cycle". The parameter talks
about scopes but the parameter values refer to life cycle instead.
Therefore it is a little confused for everyone.
The problem is that "provided" is not a real life cycle.
We need to find a new syntax for specifying two different semantics: scope and
life cycle. So for instance:
[runtime] - states for scope
runtime - states for life cycle but specifies two scopes namely compile and
runtime.
I am not sure if brackets is the right syntax for single scope. Multiple scopes
might be e.g. [compile, test].
Form my PoV the documentation needs more eyes.
> 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)
