On Feb 9, 2008 10:50 PM, limbicsystem <[EMAIL PROTECTED]> wrote: > > Hi, > > I've either discovered a bug in ivy:buildlist, or a problem with my > understanding of the <info> tag. I have two modules with the same module > name, but different organisation names. If I try to build them under a > single ant/ivy invocation, the 2nd module is removed (evicted?) from the > build, presumably because there is already a module with the same name, > albeit with a different organisation. Shouldn't the organisation attribute > distinguish the two modules?
Yes, the organisation should be used, even though usually buildlist is used with modules from the same org. But you're right, this is a bug in buildlist, only module names are used when the Map of modules/build files to sort is built. Could you please open an issue in JIRA? Xavier > > The two modules look like this: > > <ivy-module version="1.4"> > <info module="common" organisation="initech-division-A" > revision="1.0"/> > </ivy-module> > > > <ivy-module version="1.4"> > <info module="common" organisation="initech-division-B" > revision="1.0"/> > </ivy-module> > > > I'm using Ivy built from latest svn (Ivy 2.0.0-beta2-local-20080208162900- > 20080208162900), Ant 1.7.0 on OSX 10.5.1. I've attached a tar file > containing an example that demonstrates this. Please let me know if any > further information would be helpful, and thanks for your time, > > L > > http://www.nabble.com/file/p15390544/ivy-bug.tar.gz ivy-bug.tar.gz > -- > View this message in context: > http://www.nabble.com/buildlist-evicts-modules-with-the-same-name%2C-but-different-organisation-tp15390544p15390544.html > Sent from the ivy-user mailing list archive at Nabble.com. > > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
