Community
Participate
Working Groups
Build Identifier: I36I20100426M7_20100427_0752 With Auto-build off, if APT errors shows up only after Project Build, why does it disappear before Project Build? Thanks. Reproducible: Always Steps to Reproduce: 1. Turn auto build off 2. Introduce an APT error in a Java editor, save. 3. The error will not show in Problems view yet 4. Project Build, the error will show in Problems view 5. Remove the APT error in the Java editor, save. 6. The error disappears from the Problems view, even before the Project build With Auto-build off, if the error shows up only after Project Build, why does it disappear before Project Build? Thanks.
APT is built on top of the CompilationParticipant API, which doesn't expose quite the correct model needed to handle errors in both reconcile and build phases. There are some other similar problems having to do with quick fixes - see, e.g., Bug 186057 and Bug 273088. In this case I suspect that the error is getting created during the build but is getting cleared in both build and reconcile. Is this a problem for you, or is it just something you noticed? Is this happening with "Enable processing during editing" enabled or disabled? Is the processor that generates the error a Java 5 (com.sun.mirror.apt) or Java 6 (javax.annotation.processing) processor?
It is com.sun.mirror.apt.AnnotationProcessor. I don't think this is a big issue, but think this is inconsistent. Is it something that can be fixed? Thanks.
It is on the list of things that I would like to fix, but it is not at the top and the APT project's resources are painfully limited. If you would like to contribute a patch, I'd be glad to review it. Please carefully read the other mentioned bugs first, to avoid regressions; there are some complex issues underlying this.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
