Bug 38134

Summary: -nowarn options not suppressing XLint or declare warnings
Product: [Tools] AspectJ Reporter: Wes Isberg <wes>
Component: CompilerAssignee: Jim Hugunin <jim-aj>
Status: REOPENED --- QA Contact:
Severity: enhancement    
Priority: P5    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows NT   
Whiteboard:

Description Wes Isberg CLA 2003-05-27 04:01:38 EDT
When specifying compiler option "-nowarn" or "-warn:none", warnings for declare
warning and XLint are still emitted.

For declare warning, arguably, the compiler options should not apply to the
weaver.  But it might encourage the use of declare-warning if they could be
disabled at the command line.  We should document (at least here) that this is a
bug to be fixed in later releases (perhaps with a weaver-specific option) or
that the command-line warning constraints do not apply to declare warning
statements.

For XLint, the workaround is to set "ignore" as the XLint default or per-message
level, so applying the compiler options here is less compelling though still a
natural assumption -- again, worth documenting.

Tests using tests/harness/{XLint}WarningTest.java added to
tests/ajcTestsFailing.xml.  

I could not check whether the compiler options hid  a "standard" warning because
I could find none being issued, presumably intentionally due to the line in
org.aspectj.ajdt.ajc.BuildArgParser 'javaArgList.add("-warn:none");'  Might doc
that, too, if it's to be our default.
Comment 1 Jim Hugunin CLA 2003-05-27 13:38:21 EDT
All of the behavior noted below is defined as correct for ajc-1.1.0.  I 
decided that the the ajc-specific warnings should be kept separate from the 
eclipse-specific ones, and that the eclipse-specific warnings should be silent 
by default.  This gives maximum compatibility with ajc-1.0.

This arbitrary decision should be revisited for a future release (1.2?)
Comment 2 Wes Isberg CLA 2003-05-27 15:38:38 EDT
Resolving as LATER.  Caveat added to devguide/ajc.xml.
Comment 3 Eclipse Webmaster CLA 2009-08-30 02:50:33 EDT
LATER/REMIND bugs are being automatically reopened as P5 because the LATER and REMIND resolutions are deprecated.