Community
Participate
Working Groups
This bug is transferred from JDEBUG to JCORE, it is bug 22509. Summary -------- The problem was that I m not able to launch a Java application. With the JDEBUG TEAM we have see it is due to the fact that the project cannot be compiled. It happend on the last Eclipse release. Maybe important: At work I use a pre-release of Eclipse 2.0, export the project as jar and import it at home (Eclipse 2.0), where the problem occur. 1. There is no .class file in the workspace 2. I do not import the ".project" and ".classpath" file and even have verify the content, it sounds correct. Christophe
I have notice that : I do "Right click->Java Build Path" and I have the message "Build path will result in a cycle." It only occur on projects that I cannot compile ! Christophe
The Java builder will refuse to compile projects for which the classpath is invalid (so as to minimize the number of secondary errors). Note that you can change this behavior by unchecking the preference: Window>Preferences>Java>Compiler>Other>Stop building when invalid classpath is detected. Is this ok ?
Hi, Yes it is fine now ! But I do not understand why it say it has a cycle ?? What do this mean and how to correct this ?
Some cycle must be occurring if you follow the chain of prerequisite projects. Eclipse build will only build each project once, prerequisite before dependent, therefore in presence of a cycle, some prerequisite built state will be missing (several iterations of build are necessary to build clear usually in presence of cycles).
Closing, please reopen if necessary.
