Description Larry Isaacs 2010-05-06 20:58:59 EDT

If you create a dynamic web project and a utility project, then add an external jar to the Java build path of the utility project, you can use the Deployment Assembly page to mark the external jar for "publish/export" by clicking Add and using the "Referenced Projects Classpath Entries" in the New Reference Wizard.  After marking the external jar with a check and clicking Finish, the "Pull in classpath elements from referenced projects" reference gets added to the dynamic web project.  This reference causes a build path cycle which prevents the project from building.

The problem is that J2EEComponentClasspathContainer.update() is adding the referenced component from the "Pull in classpath elements..." reference to the web project's classpath, which is the web project itself, creating the cycle.  I'm not sure what mechanism is appropriate so J2EEComponentClasspathContainer will ignore this "special" reference.