Summary: | Java Build errors after save | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | jborn |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | blocker | ||
Priority: | P3 | CC: | jborn |
Version: | 1.0 | ||
Target Milestone: | 2.0 M6 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
jborn
2002-05-03 10:47:42 EDT
Seems to be an inconsistency in the JavaModel at the point the Java builder tries to initialize itself. Does it improve the behavior if going to the navigator, you close the offending project and reopen it (this force to refresh the model for this project). Note we have changed our Java builder implementation completely for the 2.0 release. Maybe you could try to get a recent stable Eclipse 2.0 build, and see if this project compiles ok with it (which I am fairly confident it will). Maybe something interesting would be to append the content of your .classpath file (located at your project root, remove .* filter). I was unable to leave my project in the build errors state. To resolve my issue I had to move my workspace and recreate each project. This allowed every project I've added back into the workspace to compile without problems and without modification. I never tried to close and reopen the projects before this. I did however close and open WSAD 4.0.3 multiply times. One other piece of information about this bug is that I created all my projects outside of the workspace. Not the default location. I also installed with CVS. Before I moved on I did save off my workspace from both the default location and the save location. What follows is the .classpath file from the offending project. However none of the projects compiled. <?xml version="1.0" encoding="UTF-8"?> <classpath> <classpathentry kind="var" path="SERVERJDK_PLUGINDIR/jre/lib/rt.jar" rootpath="src" sourcepath="SERVERJDK_PLUGINDIR/src.jar"/> <classpathentry kind="src" path="ejbModule"/> <classpathentry kind="var" path="WAS_PLUGINDIR/lib/j2ee.jar"/> <classpathentry kind="var" path="WAS_PLUGINDIR/lib/csicpi.jar"/> <classpathentry kind="var" path="WAS_PLUGINDIR/lib/ejbcontainer.jar"/> <classpathentry kind="var" path="WAS_PLUGINDIR/lib/ivjejb35.jar"/> <classpathentry kind="var" path="WAS_PLUGINDIR/lib/vaprt.jar"/> <classpathentry kind="var" path="WAS_PLUGINDIR/lib/ras.jar"/> <classpathentry kind="var" path="WAS_PLUGINDIR/lib/utils.jar"/> <classpathentry kind="output" path="bin"/> </classpath> Once again the problem wasn't the code.. It compiled through ANT. So I would also be confidant that eclipse 2.0 would compile my code. I do question wether the integration of the compiler to the GUI or how the compiler is called may have led to the issue I was having. jb The compiler is invoked through the incremental Java builder, which in this case has a defect. Therefore the Ant job can succeed, but the integrated build action fails. The good new is that we have entirely rewritten the incremental Java builder which wraps the compiler for 2.0. It is much faster and more lightweight than the 1.0 builder. I am confident that this particular problem is gone. WSAD 5.0 will be using this new Java builder code, so you should soon have a solution for this one. Closing, please reopen if symptoms were to persist once using the 2.0 code base. |