[
https://issues.apache.org/jira/browse/MCOMPILER-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413305#comment-17413305
]
Robert Scholte commented on MCOMPILER-412:
------------------------------------------
Depends on [Support
--process-module-path|https://github.com/codehaus-plexus/plexus-compiler/issues/150]
in plexus-compiler
> Support --process-module-path
> -----------------------------
>
> Key: MCOMPILER-412
> URL: https://issues.apache.org/jira/browse/MCOMPILER-412
> Project: Maven Compiler Plugin
> Issue Type: Improvement
> Affects Versions: 3.8.0, 3.8.1
> Reporter: remi forax
> Priority: Major
>
> {quote}
> In the modular world, javac will look for annotation processor in the
> module-path (only if the annotation processor module is required by the
> module-info, you can use "required static" or uses with the service) and
> javac will also look to the --processor-module-path with again a nice
> separation because the source code doesn't see the module inside the module.
> Everything works cleanly if there is no module-info.java, if you have a
> module-info.java, you have two cases
> 1) your annotation processor is itself a module, if you do a requires on it,
> Maven will put it in the module-path, so it will work (but there is no nice
> separation provided by --processor-module-path)
> 2) your annotation processor is not a module, you can do a require on it but
> Maven will not put it on the module-path because it's not a module, so you
> have to use the <processor-path> of the Maven compiler plugin
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
