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

["Stephen Kestle (JIRA)" <ji...@apache.org>]

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

Stephen Kestle commented on IVYDE-360:
--------------------------------------

Still present in 2.3.0.beta1-20140104...

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