Summary: | @SuppressWarnings for access restriction | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Ian Bull <irbull> | ||||
Component: | Core | Assignee: | Maxime Daniel <maxime_daniel> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | enhancement | ||||||
Priority: | P3 | CC: | markus.kell.r, martinae | ||||
Version: | 3.2 | ||||||
Target Milestone: | 3.2 M5 | ||||||
Hardware: | PC | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Ian Bull
2005-10-31 21:28:32 EST
Access restrictions warnings could be added to the irritant list. Philippe, any objection? Of course using "all" should be fine. We could add a "restriction" irritant indeed. Martin - would you support it in the UI ? (quickfix) Quick fix uses CorrectionEngine.getWarningToken(problem.getProblemId()); to get the token, so no changed needed on out side. Would warning token "restriction" appeal to all ? Added support in CompilerOptions. Maxime: could you add testcase (batch test likely) ? Also edit doc to mention this new warning token. Created attachment 34009 [details]
Test case (using BatchCompilerTest)
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. Thanks everyone... This is great! Looking forward to M5! - ian Verified for 3.2 M5 using build I20060214-0010 |