Community
Participate
Working Groups
After working in Eclipse 3.2 (this has happened for me in RC3-5) for some time and after making changes in several Java source files, Eclipse starts to add some error annotations to open Java sources. The compiler does not seem to have any problems compiling the class, however. The problem will not go away until I quit Eclipse and restart it. Then the bogus error annotations go away, until another short period of work. The problem seems to start happening somewhat randomly, sorry I can't provide a test case that illustrates the problem but I will attach a screen shot. I've seen some other bug reports that seem similar, but for older versions, and couldn't seem to find an open report for the 3.2 series.
Created attachment 42810 [details] Screen shot of the bogus error annotation. Here is the error annotation. Note the class itself, in the Package Explorer, does not show any compile errors (in fact there aren't any errors in this Java file).
This could be an issue in the editor reconcile action, which uses the compiler to compute on the fly errors when you type. If it is inconsistent with building, as you describe, then it indicates a bug indeed. Now, in order to address it, we would need some steps to reproduce. Could you provide your workspace, or reduce it to something smaller ?
My workspace is too large to attach, but I created a bzip2 tarball, available here: http://msqr.us/ws-3.2.tbz2 The project in this workspace is expecting the Sysdeo Tomcat plugin.
Could you please provide the workspace as a zip file ? Also where can I get the Sysdeo Tomcat plugin ? What version ? Also I'm not sure I'm allowed to download this plugin. A workspace not depending on this plugin would be prefered.
I have limited bandwidth on msqr.us, if you can work with the bzip-tar that would help greatly. Sysdeo's Tomcat plugin is available here: http://www.sysdeo.com/eclipse/tomcatplugin. The workspace is not entirely dependent on it; if you don't have the plugin then then you need to simply define a classpath variable TOMCAT_HOME.
I finally was able to uncompress your workspace. It seems that it depends on other things than the tomcat plugin. For instance, I see that the following libraries are missing: - TOMCAT_HOME\common\lib\jasper-runtime.jar - TOMCAT_HOME\common\lib\jsp-api.jar - TOMCAT_HOME\common\lib\servlet-api.jar
Yes, you need to define a classpath variable TOMCAT_HOME that points to a local Tomcat 5 directory.
The problem is how I get - jasper-runtime.jar - jsp-api.jar - servlet-api.jar Those are not included in the Tomcat plugin you indicated.
In the meantime, could you please delete org.eclipse.jdt.core_3.2.0.v_668.jar from your plugins directory, copy http://www.eclipse.org/jdt/core/patches/org.eclipse.jdt.core_3.2.0.z20060531-1812.jar to this plugins directory instead, and let me know if this improves things ?
Please ignore patch in comment 9. I identified the cause (bad side effect on a MethodInfo in the Java model cache) and posted a new patch. Could you please delete any org.eclipse.jdt.core_3.2.0.*.jar from your plugins directory, copy http://www.eclipse.org/jdt/core/patches/org.eclipse.jdt.core_3.2.0.z20060602-1334.jar to this plugins directory instead, and confirm this fixes the problem ?
If the patch fixes the problem, this bug would be a dup of bug 140879.
Sorry for not getting back sooner, I didn't seem to get bug emails for your last few comments. I'm downloading the patched JAR and will let you know if it resolves the issue for me.
The patched JAR you provided does seem to have fixed the issue for me, I have not seen the issue yet since installing it.
Thanks for the feedback. FYI the patch as been integrated in 3.2 RC7. *** This bug has been marked as a duplicate of 140879 ***
Changing OS from Mac OS to Mac OS X as per bug 185991
