You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Nicolas Lalevée (JIRA)" <ji...@apache.org> on 2009/03/31 11:25:50 UTC

[jira] Commented: (IVYDE-170) dependency order not preserved causing failed builds

    [ https://issues.apache.org/jira/browse/IVYDE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694032#action_12694032 ] 

Nicolas Lalevée commented on IVYDE-170:
---------------------------------------

I tried with a very simple project, it works for me. May with transitive dependencies the bug will show up.
Could you attach here an ivy dependency report of your project ?


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