Red underwave of filename doesn't disappear after compile error fixed

After a file which had a compile error (during Ant build) is marked with the red underwave in the Project view and in the editor tab, fixing the error and compiling again sometimes doesn't remove the red underwave. Compiling again after a further modification still doesn't remove the red underwave. Only restarting IDEA removes it. Anybody else seen this?

5 comments
Comment actions Permalink

This is a known problem where if an error caused by a JAR is then fixed
externally (i.e., the JAR is changed to fix the problem), the red underwave
won't go away until the project is reloaded. I found one related JIRA that's
marked as fixed in the recent EAP (7821):
http://www.jetbrains.net/jira/browse/IDEADEV-26164.

However, this one (which has several duplicates) is still open after almost
a year:

http://www.jetbrains.net/jira/browse/IDEADEV-17120

;ted

"Gordon Tyler" <gordon.tyler@quest.com> wrote in message
news:32859651.26851210262858631.JavaMail.jive@app4.labs.intellij.net...

After a file which had a compile error (during Ant build) is marked with
the red underwave in the Project view and in the editor tab, fixing the
error and the compiling again sometimes doesn't remove the red underwave.
Compiling again after a further modification still doesn't remove the red
underwave. Only restarting IDEA removes it. Anybody else seen this?



0
Comment actions Permalink

This is not the case that I'm seeing. My case is just a plain Java file being edited to change a method signature (manually, not through refactoring) and then upon compilation, an error in another plain Java file is discovered because method signature doesn't match. Double-clicking the error in the build log opens up the second Java file, I then edit it, fix the error, but the error highlighting of the filename doesn't disappear. Nor does it disappear after recompiling successfully.

0
Comment actions Permalink

What build are you running? This was an issue, see IDEADEV-26164, for a while. JetBrains was having trouble tracking it down. (See this thread for a discussion on it.) But the release notes for build 7821 show it as fixed. I'm running 7821 and it does seem to be resolved. If you are still experiencing it in 7821, you'll probably want to post a comment to the JIRA.

0
Comment actions Permalink

I'm using the 7.0.3 release which is build 7757. So you're saying this has been fixed for the upcoming 7.0.4 release?

0
Comment actions Permalink

yes; 7821 is a 7.0.4 EAP

0

Please sign in to leave a comment.