[
http://jira.codehaus.org/browse/MANTTASKS-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175439#action_175439
]
Dennis Lundberg commented on MANTTASKS-147:
-------------------------------------------
I am -1 to this change as it has been implemented. This will break *lots* of
builds, including the ones at my day job. I would be OK with it, if it was
available through a configuration option that was turned off by default.
Something like
{code}
singleScope="true/false"
{code}
If you are using Maven Ant Tasks together with Ant, you have to think like
"Maven" when it comes to dependencies. You can't think like "Ant".
> Improvements to scope filtering
> -------------------------------
>
> Key: MANTTASKS-147
> URL: http://jira.codehaus.org/browse/MANTTASKS-147
> Project: Maven 2.x Ant Tasks
> Issue Type: Improvement
> Components: dependencies task
> Reporter: Paul Gier
> Assignee: Paul Gier
> Fix For: 2.0.10
>
>
> The ant tasks currently use the standard maven artifact [scope
> filtering|https://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.10/maven-artifact/src/main/java/org/apache/maven/artifact/resolver/filter/ScopeArtifactFilter.java].
> This means that setting "useScope" to "compile" actually includes the
> scopes "compile", "runtime", and "system". This is not intuitive to a
> typical ant user.
> A better behaviour is for the the useScope attribute to allow a comma
> separated list of specific scopes to include. So for example, setting
> useScope to "compile, provided" would only include artifacts that have one of
> these two scopes set.
--
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
