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.

Bug 145689 - Adding @Override annotation using editor hints is painful when done for an entire interface
Summary: Adding @Override annotation using editor hints is painful when done for an en...
Status: RESOLVED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: Editor (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker with 1 vote (vote)
Assignee: Jan Lahoda
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-30 16:54 UTC by Chris Webster
Modified: 2013-08-10 14:53 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Webster 2008-08-30 16:54:34 UTC 
The editor hints for @Override allow adding the annotation on a per method basis. This is a problem if I have an
existing class with a large number of hints for the same interface. Having some additional options for this hint like
add @Override for all methods from 'A Class' [where a class has methods which are being overridden] and add @Override
for all possible methods in this class would save me a lot of time and clicking.
Comment 1 markiewb 2013-08-10 14:53:11 UTC 
Since 7.3 there is a submenu which allows you to apply the hint to a wider scope. For example the same file, same package or the whole project.

http://wiki.netbeans.org/NewAndNoteworthyNB73#Run_inspections.26transform_for_wider_scope_from_fixable_hint_in_editor

So resolving as worksforme.

BTW: @Override as saveaction is requested by https://netbeans.org/bugzilla/show_bug.cgi?id=227372