> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Friday, April 15, 2005 9:00 AM > To: Maven Developers List > Subject: Re: maven and ivy > > > 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. >
Sorry no time for that these days. But the main reason why I have sent "lengthy response" was to explain to ivy people that the feature they are after is already supported by maven2 metadata (poms) as it was not well communicated and probably not so obvious even to early adopters of m2. I also wanted to explain to you what I meant by "group dependencies". > 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 so now I am glad that I haven't tried to test it as I may had false impressions :) > 2) it might be more useful to pull in the modules instead of the > dependencies when doing this (e.g. depending on wagon-providers > would get > what you want, rather than creating another aggregating pom). I'll put > it in JIRA for alpha-3. > I haven't tested how this feature works in this version of maven but I did test it before and in fact I fell that few more additions are needed to make it useful. For example the necessity of saying that some dependency should not be resolved transitively (I know that you are thinking about including this feature). If you want to "to pull in the modules instead of the dependencies" it will also nice to have some control over it (e.g. different dependency type for that) Note also that in case of wagon providers there are two "competing" jars: http and http-lightweight. One of the reasons why group dependencies could be useful is exactly for giving the possibility of choosing only once which one of them should be used by default in your projects if you are using multiple wagons very often. regards Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
