You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Varga (JIRA)" <ji...@codehaus.org> on 2010/03/29 03:11:23 UTC

[jira] Issue Comment Edited: (MCOMPILER-75) Add apt support for Java 6

    [ http://jira.codehaus.org/browse/MCOMPILER-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215840#action_215840 ] 

Robert Varga edited comment on MCOMPILER-75 at 3/28/10 8:09 PM:
----------------------------------------------------------------

The proper implementation of -processorpath is really not possible with Maven as I see it at the moment.

The biggest problem is that Maven does not support a thing like tools classpath, a path which jars which the compiler itself needs but must not be on the compile or test or runtime classpath of the just compiled module.

This likely could be introduced possibly with yet another scope (or more).

Not only the processor path, but also the antrun plugin could also benefit from such a new classpath entity.

Currently the only workaround which exists is defining such dependencies with the provided scope, which at least does not trigger propagation of these dependencies, but it still puts such dependencies on the compilation classpath of the module, so compilation itself is possibly providing incorrect results.

Of course, this is just my opinion.

Best regards,

Robert Varga

      was (Author: robvarga):
    The proper implementation of -processorpath is really not possible with Maven as I see it at the moment.

The biggest problem is that Maven does not support a thing like tools classpath, a path which jars which the compiler itself needs but must not be on the compile or test or runtime classpath of the just compiled module.

This likely could be introduced possibly with yet another scope (or more).

Not only the processor path, but also the antrun plugin could also benefit from such a new classpath entity.

Currently the only workaround which exists is defining such dependencies with the provided scope, which at least does not trigger propagation of these dependencies.

Of course, this is just my opinion.

Best regards,

Robert Varga
  
> Add apt support for Java 6
> --------------------------
>
>                 Key: MCOMPILER-75
>                 URL: http://jira.codehaus.org/browse/MCOMPILER-75
>             Project: Maven 2.x Compiler Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.0.2
>            Reporter: Mark Hobson
>            Assignee: Milos Kleint
>             Fix For: 2.2
>
>
> Apt (Annotation Processing Tool) was merged into javac in Java 6.  The compiler plugin should support this new functionality, which means supporting the following new arguments:
> {noformat}
>   -proc:{none,only}          Control whether annotation processing and/or compilation is done.
>   -processor <class1>[,<class2>,<class3>...]Names of the annotation processors to run; bypasses default discovery process
>   -processorpath <path>      Specify where to find annotation processors
>   -s <directory>             Specify where to place generated source files
>   -implicit:{none,class}     Specify whether or not to generate class files for implicitly referenced files
>   -Akey[=value]              Options to pass to annotation processors
> {noformat}
> Note that this should supersede the Apt Maven Plugin at Mojo by encompassing all of its functionality:
> http://mojo.codehaus.org/apt-maven-plugin/index.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira