Actually, this is a bug. I didn't have time to file it yet, but from
Maven 2.0.7 to 2.0.8 dependencies within the <plugin> definition
suddenly are ignored in multi-module projects. Try to declare your
dependency as a normal dependency in your parent pom. Or use Maven 2.0.7.
regards,
Stefan
Niall Pemberton wrote:
I'm using the vsersion 1.2.0 of the maven-bundle-plugin from the felix
project - it has a dependency on version 0.0.227 of bndlib (groupId
"biz.aQute") and I wanted to try the plugin out with version 0.0.236
of bndlib. I tried specifying this in the plugin's dependencies both
in the dependencyManagement section and in the plugin config in the
build section:
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>1.2.0</version>
<inherited>true</inherited>
<dependencies>
<dependency>
<groupId>biz.aQute</groupId>
<artifactId>bndlib</artifactId>
<version>0.0.236</version>
</dependency>
</dependencies>
</plugin>
netiher seem to have any effect - it still used version 0.0.227 of
bndlib. The docs seem to indicate that this should work - does it, or
is this a bug?
http://maven.apache.org/pom.html#Plugins
Niall
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
