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.
Summary: | Add filter warnings possibility into the output window | ||
---|---|---|---|
Product: | projects | Reporter: | Tomas Zezula <tzezula> |
Component: | Ant | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | dstrupl |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Mac OS X | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Tomas Zezula
2010-02-26 05:48:27 UTC
You can set Ant Verbosity to a less verbose value. (Settings available from button in Output Window.) That affects all builds. But in this case the problem is the OpenJDK build scripts. These need to be passing a special compiler flag to disable warnings about usage of sun.* packages. I know jdk/make/netbeans/common/shared.xml uses -XDignore.symbol.file=true but I am not sure if this is the right flag or if there is another. (Ideally warnings about sun.* would simply be one -Xlint suboption.) Note that there is also a bug filed for javac to queue up warning messages and only display them if there are no errors, or at least to put the errors at the top or bottom of the list so they are easy to find. Note also that the NB Ant integration automatically stops scrolling the OW when (what appears to be) the first "hard" error message is printed. Why was this reopened? Comment #1 explains what needs to happen in OpenJDK build scripts. As far as I remember Igor wanted to have a filter which can filter out the warnings from the output. But if the javac Messager will print first errors and then warning. It's OK to keep it as WONTFIX. |