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

Paul Gier closed MANTTASKS-124.
-------------------------------

    Resolution: Fixed
      Assignee: Paul Gier

The issue with "useScope" is that it uses the built in scope filtering that 
Maven uses.  This is useful in some cases, but if you only want to access 
specific scopes, then the "scopes" option is simpler.  I'll close the issue 
since you said it was resolved by MANTTASKS-147.

> Setting dependencies with the provided scope does not work
> ----------------------------------------------------------
>
>                 Key: MANTTASKS-124
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-124
>             Project: Maven 2.x Ant Tasks
>          Issue Type: Bug
>          Components: dependencies task
>    Affects Versions: 2.0.9
>         Environment: OS X 10.4.11, Java 5, Ant 1.7.0, Ant 1.6.5
>            Reporter: John Gibson
>            Assignee: Paul Gier
>
> If you use the provided scope to pull in dependences like this:
> <artifact:dependencies pathId="osgi.provided.classpath" 
> filesetId="osgi.provided.fileset" verbose="true" useScope="provided">
>       <pom refid="osgi.maven.project" />
>       <remoteRepository refid="m2.repository"/>
> </artifact:dependencies>
> Then the result classpath and fileset are empty despite the POM containing 
> definitions like this:
> ...
> <dependencies>
>               <dependency>
>                       <groupId>org.osgi</groupId>
>                       <artifactId>osgi-compendium</artifactId>
>                       <version>4.1.0</version>
>                       <scope>provided</scope>
>               </dependency>
>               <dependency>
>                       <groupId>org.osgi</groupId>
>                       <artifactId>osgi-core</artifactId>
>                       <version>4.1.0</version>
>                       <scope>provided</scope>
>               </dependency>
>               ...
> </dependencies>
> I would expect to have the path/fileset contain at least those two jars (I'm 
> not sure about transitive dependencies, however).
> Other users have encountered this issue, see here:
> http://www.nabble.com/maven-ant-tasks-and-the-provided-scope-td19662878.html

-- 
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

        

Reply via email to