> -----Original Message----- > From: Tim Moore [mailto:[email protected]] > Sent: Monday, April 06, 2009 1:11 PM > To: [email protected] > Subject: Re: Bundle packaging conflicts with mvn release? > > 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. >
Thanks Tim, I'll give that a try. I'm sure I have tried that suggestion, but it is possible that I missed one thing here or there when I did it. I seem to recall having trouble with the 'type' element in particular. But I'll give it a try again. > Cheers, > > -- > Tim Moore Cheers, Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
