You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2009/05/07 17:08:45 UTC

[jira] Updated: (MANTTASKS-147) Improvements to scope filtering

     [ http://jira.codehaus.org/browse/MANTTASKS-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Gier updated MANTTASKS-147:
--------------------------------

         Assignee: Paul Gier
    Fix Version/s: 2.0.10

> 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