Maczka Michal wrote: >I also think that splitting the pom of artifact into some group is a bad >idea. But group (composite) >dependencies are about something else. They provide useful shortcut method >for including multiple artifacts in projects >via declaration of just a single dependency. > > Perhaps you should test things before posting such a lengthy response?
Depending on <type>pom</type> already works. There are a couple of caveats: 1) there is a bug where it attempts to include it on the compiler's classpath. Will fix. So it only works for runtime in alpha-1 2) it might be more useful to pull in the modules instead of the dependencies when doing this (eg depending on wagon-providers would get what you want, rather than creating another aggregating pom). I'll put it in JIRA for alpha-3. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
