I think the reasons for which it is not there (yet) is that : - When we publish, we have to publish all configuration. So all configuration should be build in the right order. - Also, having one dependency graph in one conf and an other one in a second conf that creates a circular dependency when you take the 2 conf is a source of problem.
Now it is true that the temptation might be big. An example that I already met is a module A using a module B, but in the test of B, I would like to use classes of A. In such a case, I have compile dependency from A to B, and test dependency for B to A. The problem with such approach is that you are always forced to build A and B together. Could you explain your scenario where you require a conf in buildlist? I'm curious. Gilles > -----Original Message----- > From: Jean-Baptiste Quenot [mailto:[EMAIL PROTECTED] > Sent: mardi 27 février 2007 11:47 > To: [email protected] > Subject: <ivy:buildlist> with specific configurations > > Hi there, > > I'm using <ivy:buildlist> to build recursively all required > dependencies for a given module. However, I don't seem to be able > to specify which configurations apply for setting-up this build > list. I don't want to include all dependencies. > > Does it make sense to add a conf="..." attribute to > <ivy:buildlist> or am I missing something? > > Thanks in advance, > -- > Jean-Baptiste Quenot > aka John Banana Qwerty > http://caraldi.com/jbq/
