On Feb 12, 2008 9:24 AM, VUB Stefan Seidel <[EMAIL PROTECTED]> wrote:
> 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 definition
> suddenly are ignored in multi-module projects. Try to declare your
> dependency as a normal depen
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 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 Pem
On 12/02/2008, Niall Pemberton <[EMAIL PROTECTED]> wrote:
>
> No-one any ideas on this?
Hi Niall,
If you're unable to get this working you can always try the 1.2.1-SNAPSHOT
that uses the new bndlib, available from the Apache snapshot repository or
over at http://repository.ops4j.org/mvn-snapshot
No-one any ideas on this?
Niall
On Feb 4, 2008 6:34 AM, Niall Pemberton <[EMAIL PROTECTED]> 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
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 dependencyManag