Community
Participate
Working Groups
Last night our build reported compiler errors from files that I had checked in. This morning I launched Eclipse (M7) and assured myself that there were no compiler errors in my code. I dismissed the problem as an anomoly, and went back to work. I eventually opened the RemittanceEngineConsole.java file and noticed a genuine compiler error that was not reported outside of that file (i.e. either the Package Explorer or Problems view).
is it reproducible?
Created attachment 8660 [details] Screenshot of hidden compiler error
I deleted the offending line, and saved and no errors were reported. I then pasted the exact same line (with the error) back in and the error within the file reappeared, but no entry went to the Problem view and the Package explorer does not show an error adornment anywhere in the project hierarchy.
Seems to be an error that is only detected by the reconciler, but not by the compiler.
This was happening quite regularly yesterday, and most definitely with errors that the compiler should recognize. For example, the error in the screenshot I provided show an attempt to call a constructor with an invalid argument type. This obviously shouldn't compile (and doesn't if you rebuild all).
With latest build, the update of the problem view is in the background. So you might not get it right away. Could you please provide a test case and attach it to this PR? Thanks.
I understand that build results are udpated asyncronously with this build. However, there were no builds in progress, and this remained this way for literally hours. I'll try to generate an isolated test case, but I'm not sure I can do that without sending along our entire source tree.
Please reopen once steps are available.
Closing as never got requested information
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
