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: | Show as for standard javac warnings cannot be customized | ||
---|---|---|---|
Product: | java | Reporter: | Jiri Prox <jiriprox> |
Component: | Hints | Assignee: | Jan Lahoda <jlahoda> |
Status: | REOPENED --- | ||
Severity: | blocker | CC: | err, matthies, rmatous, tmysik, tzezula |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Jiri Prox
2008-01-15 15:08:26 UTC
*** Issue 139028 has been marked as a duplicate of this issue. *** Really P4 and TM future? So wouldn't it be better to remove it from UI? Agree with Tomas. No problem if this feature won't be delivered for 6.5, but as soon as somehow implemented and visible in UI then should be fixed. If impossible to fix then UI should reflect the fact that this feature isn't implemented. Resolving all issues with milestone "future" as LATER. If you feel strongly that it should be implemented please reopen and set the target milestone to "next". NetBeans.org Migration: changing resolution from LATER to WONTFIX This bug is driving me nuts, why was it set at "won't fix?" The inability to find unorganized/unused import statements without going through files one at a time is extremely annoying. Reopening; could this issue be evaluated again, please? Thanks. *** Bug 188394 has been marked as a duplicate of this bug. *** *** Bug 252632 has been marked as a duplicate of this bug. *** 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 Still reproducable in current dev build. |