Hi, On Wed, Nov 18, 2009 at 4:08 PM, Justin Edelson <[email protected]> wrote: > ...You use: > <defaultBundles> > <version>6-SNAPSHOT</version> > </defaultBundles> > > This is actually pretty close to what Bertrand suggested (sorry for doubting > you...). The nice thing is that this element is entirely optional. For both > base, defaultBundles, and web support (i.e. pax-web), there are reasonable > defaults. And if you want to override the version, you *only* have to > override the version, not the groupId or artifactId....
But you can still override them, right? <defaultBundles> <groupId>foo.bar</groupId> <artifactId>myOwnCustomCollectionOfDefaultBundles</artifactId> <version>6-SNAPSHOT</version> </defaultBundles> I'm too ignorant about Maven plugins to tell from your code ;-) > ...Here are the poms, post modification: > http://github.com/justinedelson/sling/tree/init-package-maven/launchpad/app/pom.xml > http://github.com/justinedelson/sling/tree/init-package-maven/launchpad/webapp/pom.xml > http://github.com/justinedelson/sling/tree/init-package-maven/launchpad/testing/pom.xml Very cool! Maybe the init-package goal could be just "package"? As long as that does not conflict with Maven builtins...this is what the plugin is doing, creating a runnable Sling war or jar package. -Bertrand
