[MCOMPILER-203] Allow compiler-plugin to specify annotation processor dependencies

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3.2, 3.1
• Fix Version/s: 3.5
• Environment: Java 6+
• Assignee: Andreas Gudian
• Reporter: David M. Lloyd
• Created: 21/Mar/13 06:59
• Updated: 21/Jul/22 06:09
• Resolved: 15/Jan/16 23:30

Description

Right now the status quo for annotation processor artifacts requires one of two actions:

1. Use an external plugin for annotation processing
2. Put the annotation processor in as a dependency with provided scope

The former is suboptimal because the external plugins are clunky and ill-supported, and inflexible/hard to use. The latter is suboptimal because it is often the case that you do not want to leak annotation processor classes on to the application class path.

It should be possible to add annotation processor dependency artifacts to the compiler plugin configuration such that they are recognized by the annotation processing search algorithm of the compiler, but they do not actually appear on the compilation class path. Ideally they would also be isolated from one another (dependency graphs and all), but that's more of a "nice to have".

Issue Links

• duplicates: MCOMPILER-134 add support for jdk 6 javac -processorpath parameter
• is depended upon by: MCOMPILER-204 Add a switch to disable unwanted annotation processors
• is duplicated by: MCOMPILER-207 Support separate GAV list for annotation processors
• is related to: MCOMPILER-264 Isolate annotation processors from one another
• links to: GitHub Pull Request #114
• links to: GitHub Pull Request #117
• links to: GitHub Pull Request #128