Hi, Personally, I don't thing it is useful. It adds an additional concept that will make the adoption of ivy a little bit more complexes (very slightly I agree, but it is still a new tag).
I fear that a new user might interpret this tag as something else than a syntactic shortcut. Also the usage of the rev attributes might raise some questions that are avoided with the current syntax (what did I have to change if I want to use a patched version of spring-aop?) It is just my personal opinion, and other might thing differently, but I think the existing syntax is easier to read, and not really much longer to write (actually I think it is shorter to write as there is the same number of cut&paste, but not the 'group' tag to write). It was just my 2 cents opinion. As I said, other might thing differently. Gilles > -----Original Message----- > From: Xavier Hanin [mailto:[EMAIL PROTECTED] > Sent: vendredi 9 mars 2007 9:26 > To: [email protected] > Subject: grouping dependencies > > Hi All, > > I'm currently working on a project relying on Ivy to manage its > dependencies, and leveraging maven 2 repository. After fixing some bugs in > pom parsing, it now works pretty well. But there is one thing I notice > whlie > working with maven 2 repo is that I often have to declare dependencies on > a > set of modules from the same org (groupId in maven 2). For instance: > <dependency org="org.springframework" name="spring-core" > rev="2.0.2" > /> > <dependency org="org.springframework" name="spring-beans" > rev="2.0.2" > /> > <dependency org="org.springframework" name="spring-aop" > rev="2.0.2" > /> > <dependency org="org.springframework" name="spring-hibernate3" > rev=" > 2.0.2" /> > > Obviously I should better use an ivy variable for the revision, but it's > still very verbose IMO. So I was thinking about a new syntax, very easy to > implement (handled only as a shortcut, do not modify ModuleDescriptor > structure), allowing to group a set of dependencies by specifying some > attributes only once. For instance: > <group org="org.springframework" rev="2.0.2"> > <dependency name="spring-core" /> > <dependency name="spring-beans" /> > <dependency name="spring-aop" /> > <dependency name="spring-hibernate3" /> > </group> > > What do you think? Is it something that could help, ugly or wonderful? > > - Xavier
