[
https://issues.apache.org/jira/browse/IVYDE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Johnston updated IVYDE-170:
--------------------------------
Attachment: Screenshot.jpg
Attached is a screenshot showing jacorb-core-2.2.4.jar appearing before
orbacus.core-4.1.2.jar when expanding the ivy.xml node in eclipse. In the
dependencies below you can see that orbacus appears before jacorb. The build
works fine from the command line but fails in eclipse.
<dependency org="org.jibx" name="jibx-run" rev="1.1.3"
conf="runtime" />
<dependency org="quartz" name="quartz" rev="1.5.2"
conf="runtime" />
<dependency org="com.orbacus" name="notify-core" rev="2.0"
conf="runtime" />
<dependency org="log4j" name="log4j" rev="1.2.12"
conf="runtime" />
<dependency org="com.orbacus" name="orbacus-core" rev="4.1.2"
conf="runtime" />
<dependency org="com.orbacus" name="orbacus-event" rev="4.1.2"
conf="runtime" />
<dependency org="javax.jms" name="jms" rev="1.1" conf="runtime"
/>
<dependency org="javax.servlet" name="servlet-api" rev="2.3"
conf="runtime" />
<dependency org="com.oracle" name="ojdbc14" rev="10.2.0.3.0"
conf="runtime" />
<dependency org="org.jacorb" name="jacorb-core" rev="2.2.4"
conf="runtime" />
<dependency org="commons-logging" name="commons-logging"
rev="1.1.1" conf="runtime" />
> 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.
