ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "George Armhold (JIRA)" <j...@apache.org>
Subject [jira] Created: (IVY-731) buildlist evicts modules with the same name, but different organisation
Date Sun, 10 Feb 2008 18:35:07 GMT
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-beta-1, 2.0.0-alpha-2, 2.0.0-alpha-1
         Environment: Ant 1.7.0, Java 1.4.2, OSX 10.5.1
            Reporter: George Armhold
         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: 

   <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'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.


Mime
View raw message