Bug 578050 - Provide an option for compiler errors/warnings configuration
Summary: Provide an option for compiler errors/warnings configuration
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.9.7   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-04 13:55 EST by Eduardo Simioni CLA
Modified: 2022-01-04 14:00 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 Eduardo Simioni CLA 2022-01-04 13:55:32 EST 
When using ecj via Maven it is possible to configure compilation errors/warnings via "plugin -> configuration -> compilerArguments -> properties", pointing to a properties file that follows the Eclipse preferences standard (epf), example:

org.eclipse.jdt.core.compiler.problem.localVariableHiding=error
org.eclipse.jdt.core.compiler.problem.methodWithConstructorName=error
...
etc


I have define all compilation errors for our company so that our Maven build fails if undesired code is present, but we have several projects that use aspects and are currently not able to have that kind of check.


It would be great if ajc could also provide this option.