Bug 114456 - @SuppressWarnings for access restriction
Summary: @SuppressWarnings for access restriction
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: 3.2 M5   Edit
Assignee: Maxime Daniel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-31 21:28 EST by Ian Bull CLA
Modified: 2006-02-14 08:46 EST (History)
2 users (show)

See Also:

Attachments
Test case (using BatchCompilerTest) (4.94 KB, patch)
2006-02-02 06:58 EST, Maxime Daniel CLA 		no flags Details | Diff
View All 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 Ian Bull CLA 2005-10-31 21:28:32 EST 
I should be able to suppresswarning for a warning caused by an access
restriction.  I'm sorry if this is possible, but it doesn't work through
auto-correct, and I can't figure out the name of the warning to suppress.
Comment 1 Olivier Thomann CLA 2006-01-27 14:12:39 EST 
Access restrictions warnings could be added to the irritant list.
Philippe, any objection?

Of course using "all" should be fine.
Comment 2 Philipe Mulet CLA 2006-01-28 08:12:36 EST 
We could add a "restriction" irritant indeed.
Martin - would you support it in the UI ? (quickfix)
Comment 3 Martin Aeschlimann CLA 2006-01-29 17:23:30 EST 
Quick fix uses
 CorrectionEngine.getWarningToken(problem.getProblemId());
to get the token, so no changed needed on out side.
Comment 4 Philipe Mulet CLA 2006-01-30 05:12:22 EST 
Would warning token "restriction" appeal to all ?
Comment 5 Philipe Mulet CLA 2006-02-02 05:11:31 EST 
Added support in CompilerOptions.
Maxime: could you add testcase (batch test likely) ? Also edit doc to mention this new warning token.
Comment 6 Maxime Daniel CLA 2006-02-02 06:58:43 EST 
Created attachment 34009 [details]
Test case (using BatchCompilerTest)
Comment 7 Maxime Daniel CLA 2006-02-03 04:47:32 EST 
Since the list of warning tokens has no natural home in the documentation yet (only cited into 'What's new in version 3.1' section), I close the bug without editing the doc. Olivier offered to determine the best place to add a complete list of the supported warning tokens, which will complete the doc requirements.
Comment 8 Ian Bull CLA 2006-02-03 10:52:40 EST 
Thanks everyone... This is great!  Looking forward to M5!

- ian
Comment 9 Jerome Lanneluc CLA 2006-02-14 08:46:07 EST 
Verified for 3.2 M5 using build I20060214-0010