- This topic has 4 replies, 3 voices, and was last updated 20 years, 9 months ago by
.
-
Posts
-
Hi,
I’m running MyEclipseIDE 2.7RC2 on Windows 2000 with Tomcat 5.0.14. I sync to a CVS archive running on Red Hat 9.0
I’m getting sporadic compilation failures related to a missing library – J2EE 1.3 Library
When viewing the “Java Build Path” in the project’s properties I see a small icon against the J233 Library indicating some problem. I tried deleting the library and then adding it again, but although I can select the library from the list in the “Add Library” dialog, the “Next” button does nothing.
There is a workaround:
1. Delete the library.
2. Close the project
3. Close Eclipse
4. Open Eclipse
5. Open the project
6. View the project’s properties
7. View the Java Build Path
8. “Add Library” to add the J2EE 1.3 Library.
9. Force a complete rebuild of the project.Everything is then fine. This problem happens randomly. I can’t see any pattern at the moment.
FYI, this happened in RC1 and RC2.
Regards
Darren.
Darren,
Thanks for posting the problem and the workaround. We haven’t been able to reproduce it internally on the 2.7 GA release build, but that doens’t mean you won’t see it again either. What version of Eclipse are you running? I’ve seen problems with 2.1.0 in forgetting items on the buildpath, but I think these were addressed in the subsequent patches.
If you manage to isolate the steps that cause this, please let us know.
Hi
Win2K, eclipse 2.1.2, myeclipse 2.7RC2, j2sdk1.4.2_03
I’m having the same trouble from time to time, sometimes after having updated a plugin.
I’ve found a simpler workaround :
Window/preferences/MyEclipse/J2EE/Library Sets/J2EE 1.3 :
check “Disable Library set?” , then uncheck it and OK.Dom
Hi,
I’m running Eclipse 2.1.1.
I’ll post more information as this happens again.
Would you recommend upgrading to the latest 2.x Eclipse release?
Regards
Darren.
Darren,
I never recommend destabilizing a working configuration due to the risk it involves. 🙂
However, if the library issue is proving problematic, it may be something that was fixed in 2.1.2. However, 2.1.3 should be days away from release (they’re at RC2 with it now), so if you upgrade I’d wait for that. One thing I should point out is that you shouldn’t use the Install / Update manager to upgrade with MyEclipse installed as it may be problematic. I’d recommend doing a clean 2.1.3 installation and reinstalling MyEclipse on that. Once you have it working with a clean workspace, you can shutdown and point the new configuration to your existing workspace with the -data commandline arguement. This way, if you have any trouble at all, you can always toss the new config and continue using your tried and true one. Much less risk this way.
