I'm still wrapping my head around OSGi in general, but when it comes to delivering the bundles there seem to be a number of options around.
The Maven cookbook suggests the pax plugin from OPS4j: http://www.ops4j.org/projects/pax/construct/maven-pax-plugin/ Felix has the maven-bundle-plugin: http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html Is there an emerging standard for this? Will the maven project eventually maintain a plugin for osgi packaging (if that's even an appropriate term here, would it be more of a classifier)? Or is it too early in the OSGi game to ask that question? We are considering dm Server, which seems to like the PAR format, but SpringSource's plugin for it: http://static.springsource.com/projects/dm-server/1.0.x/getting-started/html/ch07s04.html http://blog.springsource.com/2009/06/24/maven-par-plugin-100m1/ ... seems to overlap (group and artifact! org.apache.maven.plugins:maven-par-plugin) with: http://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/maven-par-plugin/ which makes me nervous, since I *think* that is a completely different PAR format. Was SpringSource just on crack when they used that groupId? I would have expected them to use com.springsource.something. Are they working with the Maven project on this? The Maven POM reference says "The current core packaging values are: pom, jar, maven-plugin, ejb, war, ear, rar, par." Which "par" is this referring to? I assume the old one. And yet where's the plugin for it? Is that *not* a core packaging value? http://maven.apache.org/pom.html Sigh. Any insight would be appreciated. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
