[
https://jira.codehaus.org/browse/MCOMPILER-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=352025#comment-352025
]
David M. Lloyd commented on MCOMPILER-203:
------------------------------------------
An important note here would be that the processors should have their own
dependency resolution and class loading scope, so that the versions of
dependencies of the annotation processor do not have an impact on the versions
used to compile the project itself (or other annotation processors).
They should have their own {{<dependencies>}} and {{<exclusions>}} and so on.
> Allow compiler-plugin to specify annotation processor dependencies
> ------------------------------------------------------------------
>
> Key: MCOMPILER-203
> URL: https://jira.codehaus.org/browse/MCOMPILER-203
> Project: Maven Compiler Plugin
> Issue Type: New Feature
> Affects Versions: 2.3.2
> Environment: Java 6+
> Reporter: David M. Lloyd
>
> Right now the status quo for annotation processor artifacts requires one of
> two actions:
> # Use an external plugin for annotation processing
> # 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".
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
