ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <j...@apache.org>
Subject [jira] Resolved: (IVYDE-170) dependency order not preserved causing failed builds
Date Sat, 09 Jan 2010 18:20:54 GMT

     [ https://issues.apache.org/jira/browse/IVYDE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nicolas Lalevée resolved IVYDE-170.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.0
         Assignee: Nicolas Lalevée

Whereas I was not capabale of reproducing the bug, I find some little difference between IvyCacheTask
and IvyDE. So now IvyDE is having the exact same algorithm as IvyCacheTask. I hope it will
fix the bug. You are welcomed to reopen if this is not the case.


> dependency order not preserved causing failed builds
> ----------------------------------------------------
>
>                 Key: IVYDE-170
>                 URL: https://issues.apache.org/jira/browse/IVYDE-170
>             Project: IvyDE
>          Issue Type: Bug
>          Components: classpath container
>    Affects Versions: 2.0.0.beta1
>         Environment: eclipse ganymede on redhat linux
>            Reporter: Jeff Johnston
>            Assignee: Nicolas Lalevée
>             Fix For: 2.1.0
>
>         Attachments: Screenshot.jpg
>
>
> When I expand the ivy.xml tree in the package explorer the jar files are not in the same
order they are in the ivy.xml file on the system. In one particular case we have multiple
corba libraries with conflicting method signatures. Building on the command line works but
building in eclipse picks up the wrong jar first and thus fails. In another case we have multiple
XML implementation jars. Building on the command line works but building in eclipse picks
up the wrong jar first and does not compile.

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