Well, it did take too long. The problem seemed to be due to my using the *released* beta ivy plugin and the *trunk* ivyde plugin. Once I built the ivy plugin from trunk and deployed it, not only did the classpath container flakeyness go away, a bunch of other minor issues also went away. Now I am very happy!
cheers -- View this message in context: http://www.nabble.com/Experience-report-with-IvyDE-trunk-and-%22Resolve-dependencies-in-workspace%22-tp19134941p19135234.html Sent from the ivy-user mailing list archive at Nabble.com.
