This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Red error text in both cases: R 164, G 0, B 0 Blue underlined links in both cases: R 0, G, 0, B 178 We get "warning: [unchecked] unchecked conversion ..." but we get "unreported exception ..." Note the lack of an error qualifier so there is nothing to search for errors in the log. So if there are more than a handful of warnings then an error in between them cannot be found.
The IDE follows how Ant's <javac> reports these, which is at MSG_WARN even for errors. I am not sure whether it is possible for that task to use MSG_ERR for compiler errors in the case of the internal compiler; definitely not possible for a forked compiler. Would be possible if updated to use JSR 199 (internally). The Ant runner module could perhaps search for well-known strings in output such as "warning: " or "error: " and differentiate this way. Not sure how reliable this will be. Anyway the lack of a color distinction may be a red herring here (sorry) since the main problem is that javac even reports warnings when there are hard errors (and intermixes them), which is already reported as #6764649.
Created attachment 116312 [details] Experimental patch Shows at least message after hyperlink in a warning color when starts with "warning: ". But lots of other output is sent at MSG_WARN, i.e. red, and the result is confused.
I agree that color is not the main issue because even the label of an error message is missing (the label of a warning message is "warning:"). So that is a red herring. My primary concern is that there is absolutely no reliable way to find an error message in the output although it is reported in the count. Quite unbelievable and irritating. How can we be asked to be patient with a situation where we cannot tell what the reason is for a compilation process failure. Fix hunders of warnings first? That is what I had to do. I hope that this will be fixed some time cleanly - via JDK bug #6764649 or otherwise. Meanwhile thanks for the experimental colour fix - I appreciate this. But I am not sure whether this is the long term solution especially if it somehow disguises or blurs the fundamental problem.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss