Bug 335810 - Suppressing raw type warnings with AspectJ
Summary: Suppressing raw type warnings with AspectJ
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 normal with 1 vote (vote)
Target Milestone: 1.6.12   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-31 02:35 EST by Emond Papegaaij CLA
Modified: 2011-05-03 10:57 EDT (History)
3 users (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 Emond Papegaaij CLA 2011-01-31 02:35:10 EST 
Build Identifier: 

Starting with Eclipse 3.6, the Eclipse compiler no longer suppresses raw type 
warnings with @SuppressWarnings("unchecked"). You need to use 
@SuppressWarnings("rawtypes") for that. Is it possible to change this in the 
AspectJ compiler as well?

At our company, we have several libraries shared between projects. Some of 
these projects use AspectJ, where others are still plain Java to compile these 
libraries. The current behavior makes it impossible to suppress raw type 
warnings in both compilers: with 'unchecked', Eclipse 3.6 will complain about 
raw types and with 'rawtypes', AJDT complains about an unknown 
SuppressWarnings token.

Reproducible: Always
Comment 1 Andrew Clement CLA 2011-04-27 20:06:02 EDT 
Fixed!  I ported the 3.6 behaviour back into AspectJ.  Now rawtypes works as expected.  This will be in AJDT tomorrow and is in a 1.6.12.BUILD-SNAPSHOT I pushed out to the test repo (maven.springframework.org).
Comment 2 Andy Wilkinson CLA 2011-05-03 10:57:17 EDT 
Thanks, Andy. Just upgraded to the latest AJDT build on the update site and a tonne of warnings have now disappeared.