Bug 165512 - Suppress Xlint warnings per @SuppressWarnings
Summary: Suppress Xlint warnings per @SuppressWarnings
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.0.6   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: 1.6.8   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-22 14:37 EST by Hermann Voßeler CLA
Modified: 2010-01-26 15:23 EST (History)
1 user (show)

See Also:

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 Hermann Voßeler CLA 2006-11-22 14:37:53 EST 
You can configure Xlint warnings via the JDT/Compiler preferences page,
even on a per project base. But seemingly you can't use the 
@SuppressWarnings-Annotation to switch off this warnings for individual
locations. You can only use some standard tokens for this annotation (e.g.
for unchecked generics). This renders some of this warnings almost useless.

So the request is: make the eclipse java compiler recognize the
Xlint warning IDs for @SuppressWarnings
Comment 1 Olivier Thomann CLA 2006-11-22 20:30:32 EST 
Could you please enumerate the warnings that you would like to see covered?
We have a extensive set of options, but none of them correspond to a swallowedExceptionInCatchBlock option.
This seems to be an aspectj option. I don't see how we could add a SuppressWarning for an option that is not in our set of options.
Moving to Aspectj
Comment 2 Andrew Clement CLA 2007-10-26 03:45:14 EDT 
something we can do here in 1.5.4?
Comment 3 Andrew Clement CLA 2010-01-26 15:23:25 EST 
SuppressAjWarnings is supported