maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David M. Lloyd (JIRA)" <>
Subject [jira] (MCOMPILER-203) Allow compiler-plugin to specify annotation processor dependencies
Date Thu, 12 Mar 2015 14:50:18 GMT


David M. Lloyd commented on MCOMPILER-203:

Example configuration:

                                <!-- top-level exclusions here -->
                                <!-- extra dependencies here -->

If no {{<processors>}} element is given, then discovery should behave as it does today;
if a {{<processors>}} element is present but empty then no annotation processors should
be discovered.

> Allow compiler-plugin to specify annotation processor dependencies
> ------------------------------------------------------------------
>                 Key: MCOMPILER-203
>                 URL:
>             Project: Maven Compiler Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.3.2, 3.1
>         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

View raw message