Bug 20261

Summary:	cycle in classpath detection seems overzealous
Product:	[Eclipse Project] JDT	Reporter:	Brett Neumeier <random>
Component:	Core	Assignee:	Philipe Mulet <philippe_mulet>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	2.0
Target Milestone:	2.0 F4
Hardware:	All
OS:	All
Whiteboard:

Description Brett Neumeier

2002-06-13 15:16:34 EDT

I have two projects, each of which uses code from the other.  They are different
projects because different parties are responsible for the code in each project.

In previous versions of Eclipse, this was fine.  However, in the F2 and F3
stable builds, I find that this is treated as a bug:  Eclipse complains that
there is a cycle in the project's classpath, and refuses to build either
project.

This seems to me a fairly straightforward usage pattern, and I don't understand
why it would be made impossible.  I would like this behavior to be either
reverted or made configurable through the use of some property setting.

Alternatively -- if there is a good reason to prevent projects from sharing code
with each other -- how should I handle these two projects?

Thanks,

Brett Neumeier

Comment 1 Philipe Mulet

2002-06-14 05:53:17 EDT

The Eclipse build management will build each project once exactly, and ensuring 
that prereq projects are built first. Therefore, in presence of cycles, the 
build process may result in inconsistencies.

This is why we added this behavior to the Java builder, so as to make sure that 
users don't get hit by such inconsistencies by mistake. Now, if you still want 
to proceed in this mode, knowing what you do, just uncheck the Java compiler 
setting:

Window>Preferences>Java>Compiler>Others>Stop building when invalid classpath is 
detected