Bug 419279 - ajc option to change -Xlint level per-message without Xlintfile
Summary: ajc option to change -Xlint level per-message without Xlintfile
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.7.3   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 1.7.4   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-11 15:20 EDT by Rob Platt CLA
Modified: 2013-10-23 15:45 EDT (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 Rob Platt CLA 2013-10-11 15:20:08 EDT 
The -Xlintfile option is not a great fit for controlling message across multiple build projects, specifically in my case from the pluginManagement section of a maven parent pom. The problem is that you need a local file to configure the per-message output levels (ignore/warning/error) when you really want to specify it in the build script or in a shared file.

As an alternative to -Xlintfile, it would be handy to be able to change an Xlint warning level per message using command line options.

For example:

ajc -Xlint:adviceDidNotMatch=ignore

would override the XlintDefault.properties file for the adviceDidNotMatch message.

With Regards
Rob
Comment 1 Andrew Clement CLA 2013-10-23 15:45:17 EDT 
fixed. -Xlint: can take a comma separated list of name=value pairs.