[IVYDE-360] NoClassDefFoundError with multiple exported projects' ivys

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.2.0.final
• Component/s: launch configuration

Environment

Eclipse Kepler and SR1, Ivy 2.3.0

• Assignee: Unassigned
• Reporter: Stephen Kestle
• Created: 22/Jan/14 02:08
• Updated: 31/Jan/14 01:03

Description

When I have 3 projects exporting ivy.xml only 1 of the first 2 projects will export (depending on export order).

A: Exports ivy.xml
B: Imports A and Exports A then it's own ivy.xml
C: Imports B

Compilation works, but only A's ivy will be on the runtime classpath (determined via observation). If B exported it's own ivy.xml then A, then only B's ivy would be on the classpath.

I have verified that my Indigo environment running 2.1 works, and that Helios with 2.2.0 beta1 fails (as does kepler with 2.2.0 beta1)