Bugzilla – Full Text Bug Listing
| Summary: | Suppressing raw type warnings with AspectJ | ||
|---|---|---|---|
| Product: | [Tools] AspectJ | Reporter: | Emond Papegaaij <emond.papegaaij> |
| Component: | Compiler | Assignee: | aspectj inbox <aspectj-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | aclement, ian, wilkinsona |
| Version: | unspecified | ||
| Target Milestone: | 1.6.12 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
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). Thanks, Andy. Just upgraded to the latest AJDT build on the update site and a tonne of warnings have now disappeared. |
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