On Apr 2, 2009, at 9:55 AM, Craig L. Ching wrote:
have you tried setting the type of your dependency to be
bundle? ie. in the "com.mqsoftware.appwise:appwise-core" pom,
it would look like this:
<dependency>
<groupId>com.mqsoftware.appwise</groupId>
<artifactId>appwise-security</artifactId>
<version>1.0.0.10</version>
<type>bundle</type>
</dependency>
this might resolve the problem - alternatively try releasing
one at a time...
Yeah, I tried that but it didn't find the bundle. I *think* it was
looking for a .bundle extension, but I might be misremembering.
We've successfully done multi-module releases with a mix of bundle
packaging and normal jars. We've discovered that the key for handling
bundle dependencies correctly is:
a) The bundle artifact should use <packaging>bundle</packaging>
b) The dependency should use <type>bundle</type>
c) The pom with the dependency needs to *also* include the bundle
plugin, with <extensions>true</extensions>. If you're missing this,
that's what will cause it to look for artifacts with a .bundle
extension.
The easiest thing we've found is to put the plugin declaration in the
parent pom for the multi-module project:
...
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<extensions>true</extensions>
<version>1.4.3</version>
</plugin>
...
</plugins>
</pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
</plugin>
</plugins>
</build>
...
This ensures that all of the modules in the project inherit the same
configuration and have the plugin activated.
Cheers,
--
Tim Moore
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
