maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thorsten Gawantka (JIRA)" <j...@codehaus.org>
Subject [jira] (MCOMPILER-203) Allow compiler-plugin to specify annotation processor dependencies
Date Mon, 20 May 2013 12:04:52 GMT

    [ https://jira.codehaus.org/browse/MCOMPILER-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=325297#comment-325297
] 

Thorsten Gawantka edited comment on MCOMPILER-203 at 5/20/13 7:03 AM:
----------------------------------------------------------------------

An example for this more than suboptimal behavior is the annotation processor for the static
static metamodel generator of eclipselink. This processor will add the complete eclipselink
dependencies to the compile-classpath which is IMHO MORE than suboptimal.

Also the version 3.1 of maven-compiler-plugin is affected ;-)
                
      was (Author: thgaw):
    An example for this more than suboptimal behavior is the annotation processor for the
static static metamodel generator of eclipselink. This processor will add the complete eclipselink
dependencies to the compile-classpath which is IMHO MORE than suboptimal.

Oh also the version 3.1 of maven-compiler-plugin is affected ;-)
                  
> Allow compiler-plugin to specify annotation processor dependencies
> ------------------------------------------------------------------
>
>                 Key: MCOMPILER-203
>                 URL: https://jira.codehaus.org/browse/MCOMPILER-203
>             Project: Maven 2.x 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message