jamon eclipse plugin seems to blow a stack trace while trying to build up classpaths.
Attached is a work around patch, but may not be the ideal solution. It got me past the issue
trunk/eclipse/uiPlugin/src/org/jamon/eclipse/ProjectClassLoader.java
...
at org.jamon.eclipse.ProjectClassLoader.addDependenciesClasspath(ProjectClassLoader.java:161)
at org.jamon.eclipse.ProjectClassLoader.classpathUrlsForProject(ProjectClassLoader.java:134)
at org.jamon.eclipse.ProjectClassLoader.addDependencyClasspath(ProjectClassLoader.java:153)
at org.jamon.eclipse.ProjectClassLoader.addDependenciesClasspath(ProjectClassLoader.java:161)
at org.jamon.eclipse.ProjectClassLoader.classpathUrlsForProject(ProjectClassLoader.java:134)
at org.jamon.eclipse.ProjectClassLoader.addDependencyClasspath(ProjectClassLoader.java:153)
at org.jamon.eclipse.ProjectClassLoader.addDependenciesClasspath(ProjectClassLoader.java:161)
at org.jamon.eclipse.ProjectClassLoader.classpathUrlsForProject(ProjectClassLoader.java:134)
at org.jamon.eclipse.ProjectClassLoader.addDependencyClasspath(ProjectClassLoader.java:153)
at org.jamon.eclipse.ProjectClassLoader.addDependenciesClasspath(ProjectClassLoader.java:161)
Anonymous
patch for ProjectClassLoader.java
Interesting. Wouldn't you have other issues with cyclical project dependencies anyway?
I work with the developer who posted this. We attempted to reproduce, but were unable to; the problem vanished on his box as well after he upgraded to Eclipse 3.5. Notably, he was using maven's eclipse:eclipse goal, so it's conceivable that this created some oddities. In any event, closing as "works for me", since there does not appear to be a "could not reproduce" option (http://xkcd.com/583/).
I still don't understand how this comes about, but I can attest that it indeed can happen.