You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@ant.apache.org by "Stephen Kestle (JIRA)" <ji...@apache.org> on 2014/01/22 03:09:19 UTC

[jira] [Created] (IVYDE-360) NoClassDefFoundError with multiple exported projects' ivys

Stephen Kestle created IVYDE-360:
------------------------------------

             Summary: NoClassDefFoundError with multiple exported projects' ivys
                 Key: IVYDE-360
                 URL: https://issues.apache.org/jira/browse/IVYDE-360
             Project: IvyDE
          Issue Type: Bug
          Components: launch configuration
    Affects Versions: 2.2.0.final
         Environment: Eclipse Kepler and SR1, Ivy 2.3.0
            Reporter: Stephen Kestle


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)



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)