In reactor mode dependent osgi bundle resolves to target/classes

[Olaf Bergner <ol...@gmx.de>]

I'm using felix' maven-bundle-plugin to wrap existing libraries - say
commons-lang - as osgi bundles. The projects that produce these wrapper
bundles - say commons-lang.osgi - reside in my workspace and are part of a
reactor build. Other projects - my own code - declare dependencies on the
artifacts - osgi wrapper bundles - produced by my 'wrapper' projects.

Everything works like a charm as long as I build my 'own' projects
separately. If, however, I do a full-fledged reactor build, as soon as maven
tries to build one of my 'own' projects that declares a dependency on an
osgi wrapper bundle, compilation fails since maven does not put the
referenced osgi bundle itself but the target/classes - say
../commons-lang.osgi/target/classes - directory from the project that
produces that bundle on the classpath used to compile my code. Obviously,
this cannot work since that directory is empty. After all, we are dealing
just with a repackaged jar.

It seems as if in reactor mode maven knows which dependencies originate from
my workspace and tries to use the class files directly. Why ist hat, and how
can I stop maven from doing so? I'm using maven 2.0.6 and
maven-bundle-plugin 0.8.0-snapshot.

Thanks for any pointers,

Olaf Bergner


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org