[MANTTASKS-124] Setting dependencies with the provided scope does not work

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.9
• Component/s: dependencies task
• Environment: OS X 10.4.11, Java 5, Ant 1.7.0, Ant 1.6.5
• Assignee: Paul Gier
• Reporter: John Gibson
• Created: 06/Dec/08 20:23
• Updated: 17/Nov/09 17:41
• Resolved: 17/Nov/09 17:41

Description

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

Issue Links

• relates to: MANTTASKS-147 Improvements to scope filtering