[ http://jira.codehaus.org/browse/MANTTASKS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=192814#action_192814 ]
John Gibson edited comment on MANTTASKS-124 at 9/29/09 6:28 PM: ---------------------------------------------------------------- The fix delivered by MANTTASKS-147 for 2.0.10 basically corrects the issue for me. useScope="provided" still doesn't work for me, but scopes="provided" does. Using the same POM that I described above, with scopes instead of useScope gives me a classpath containing all of the dependencies in the provided scope. So, I'm not sure if the issue should be closed or just downgraded from Major. was (Author: redshadow): The fix delivered by MANTTASKS-147 for 2.0.10 basically corrects the issue for me. useScope="provided" still doesn't work for me, but scopes="provided" does. Using the same POM that I described above, with scopes instead of useScope gives me a classpath containing all of the dependencies in the provided. So, I'm not sure if the issue should be closed or just downgraded from Major. > 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 > > 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