[
https://issues.apache.org/jira/browse/IVYDE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878546#comment-13878546
]
Stephen Kestle edited comment on IVYDE-360 at 1/22/14 11:28 AM:
----------------------------------------------------------------
I try not to set up launch configurations. Just use the default classpath where
possible. From my experience last week (which made me revert to my indigo 2.1
env), I could do absolutely nothing about it. Adding ivy containers directly to
a new launch configuration would never load all (whether it loaded 1 or 2 or 3
I don't know).
I have 5 projects in total, and at least 2 are having issues (I think 3). I'm
hoping to avoid creating a test scenario, but if I must... (is a workspace a
good start, or should I check out code?)
was (Author: stephenk):
I try not to set up launch configurations. Just use the default classpath where
possible. From my experience last week (which made me revert to my indigo 2.1
env), I could do absolutely nothing about it. Adding ivy containers directly to
the launch configuration would never load all (whether it loaded 1 or 2 or 3 I
don't know).
I have 5 projects in total, and at least 2 are having issues (I think 3). I'm
hoping to avoid creating a test scenario, but if I must... (is a workspace a
good start, or should I check out code?)
> 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)
