[
https://issues.apache.org/jira/browse/MCOMPILER-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054407#comment-15054407
]
Andreas Gudian commented on MCOMPILER-203:
------------------------------------------
I'm looking into this, but I'll keep it simple for now and only add the ability
to specify the {{-processorpath}} elements. So no processor-specific
argument-handling and inclusion/exclusion patterns - we shouldn't tamper too
much with the interaction of processors with the compiler.
That's how I currently imagine this:
{code}
<configuration>
<annotationProcessorPaths>
<path>
<groupId>org.sample</groupId>
<artifactId>sample-annotation-processor</artifactId>
<version>1.2.3</version>
</path>
... more ...
</annotationProcessorPaths>
</configuration>
{code}
> Allow compiler-plugin to specify annotation processor dependencies
> ------------------------------------------------------------------
>
> Key: MCOMPILER-203
> URL: https://issues.apache.org/jira/browse/MCOMPILER-203
> Project: Maven Compiler Plugin
> Issue Type: New Feature
> Affects Versions: 2.3.2, 3.1
> Environment: Java 6+
> Reporter: David M. Lloyd
> Assignee: Andreas Gudian
>
> 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.3.4#6332)
