On Wed, Nov 18, 2009 at 11:39 AM, Bertrand Delacretaz < bdelacre...@apache.org> wrote:
> <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 ;-) > Yes. For each of base, defaultBundles, and jarWebSupport, any/all of the groupId, artifactId, and version can be overwritten. You can also specify type and classifier (not sure if these will ever be used, but figured it was worthwhile to include them as options). This creates some interesting opportunities for there to be other "default bundles" collections (e.g. Day can provide a default bundles collection for Sling which includes the CRX-specific bundles). Likewise, if you didn't want to use pax-web, you could override that. What's not supported (yet) is the ability to add an additional collection of bundles (currently, you have to do this one at a time). I haven't yet figured out if this is useful or not. > > ...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. > Not to nitpick, but it's not actually creating anything. It's putting the pieces in place so when the maven-war-plugin or maven-jar-plugin executes, it has all the stuff needed to build the package. Thus, "init" or "prepare" or "setup". Theoretically, this goal could do the actual packaging, but I think that would require new Maven packaging types (sling-app and sling-webapp), which seems like a bit of overkill. Justin
