Andreas Gudian commented on MCOMPILER-276:

To be honest, the plexus implementation of the eclipse compiler binding is 
pretty much unmaintained and way behind compared to the plexus-compiler-jdt 
variant regarding passing of options and error handling:


However, that implementation currently doesn't support the 
maven-compiler-plugin option {{annotationProcessorPaths}} either. But there's a 
feature request open that you could chime in to if you'd like.

If you still want to use this for the plexus-compiler variant, then please 
check what you can do in the codehaus-plexus repository, e.g. by providing a 
PullRequest: https://github.com/codehaus-plexus/plexus-compiler - because it's 
not part of the Apache Maven project.

> Support for the compiler option annotationpath when compilerId = eclipse
> ------------------------------------------------------------------------
>                 Key: MCOMPILER-276
>                 URL: https://issues.apache.org/jira/browse/MCOMPILER-276
>             Project: Maven Compiler Plugin
>          Issue Type: New Feature
>    Affects Versions: 3.5.1
>            Reporter: ^-^
> It is impossible to set the annotationpath with the maven compiler plugin.
> The option annotationpath is used to "define the locations where to find 
> external annotations to support annotation-based null analysis". 
> (http://help.eclipse.org/neon/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Ftasks%2Ftask-using_batch_compiler.htm)
> See also https://issues.apache.org/jira/browse/MCOMPILER-123

This message was sent by Atlassian JIRA

Reply via email to