Return-Path: Delivered-To: apmail-ant-notifications-archive@locus.apache.org Received: (qmail 16474 invoked from network); 26 Mar 2008 11:31:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Mar 2008 11:31:35 -0000 Received: (qmail 75515 invoked by uid 500); 26 Mar 2008 11:31:34 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 75476 invoked by uid 500); 26 Mar 2008 11:31:34 -0000 Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ant.apache.org Delivered-To: mailing list notifications@ant.apache.org Received: (qmail 75467 invoked by uid 99); 26 Mar 2008 11:31:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Mar 2008 04:31:34 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Mar 2008 11:30:52 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 7CF9E234C0AB for ; Wed, 26 Mar 2008 04:29:24 -0700 (PDT) Message-ID: <859671867.1206530964497.JavaMail.jira@brutus> Date: Wed, 26 Mar 2008 04:29:24 -0700 (PDT) From: "Dave Watson (JIRA)" To: notifications@ant.apache.org Subject: [jira] Commented: (IVY-731) buildlist evicts modules with the same name, but different organisation In-Reply-To: <7615010.1202668507795.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/IVY-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582248#action_12582248 ] Dave Watson commented on IVY-731: --------------------------------- I've experienced the same problem and having looked at the org.apache.ivy.ant.IvyBuildList source, only the moduleId is used as the key to place ModuleDescriptors into a Map. Checkout line 196 (2.0.0-beta-1) or 205 (2.0.0-beta-2). I had a play and made a crude change of that line from: mdsMap.put(md.getModuleRevisionId().getModuleId().getName(), md); to: mdsMap.put(':' + mri.getOrganisation() + ':' + mri.getModuleId().getName() + ':', md); This appeared to fix the problem shown in your example. Hope this helps anyone fixing code. > buildlist evicts modules with the same name, but different organisation > ----------------------------------------------------------------------- > > Key: IVY-731 > URL: https://issues.apache.org/jira/browse/IVY-731 > Project: Ivy > Issue Type: Bug > Components: Core > Affects Versions: 2.0.0-alpha-1, 2.0.0-alpha-2, 2.0.0-beta-1 > Environment: Ant 1.7.0, Java 1.4.2, OSX 10.5.1 > Reporter: George Armhold > Fix For: 2.0 > > Attachments: ivy-bug.tar.gz > > > I believe there is a bug in ivy:buildlist. 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? > The two modules look like this: > > > > > > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.