[
https://issues.apache.org/jira/browse/MCOMPILER-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680375#comment-17680375
]
Petr Široký commented on MCOMPILER-496:
---------------------------------------
I believe this has been fixed as part of MCOMPILER-522.
When running the ITs (e.g. {{MCOMPILER-203-processorpath}}), I seeing am the
following output:
{code}
...
-processorpath
<base-dir>/maven-compiler-plugin/target/it/MCOMPILER-203-processorpath/annotation-processor/target/classes:<base-dir>/maven-compiler-plugin/target/local-repo/org/apache/commons/commons-lang3/3.4/commons-lang3-3.4.jar
...
{code}
which I think suggests that now the annotation-processor is "picked-up" from
the multi module build.
> The resolve process of annotationProcessorPaths is not aware of
> WorkspaceReader
> -------------------------------------------------------------------------------
>
> Key: MCOMPILER-496
> URL: https://issues.apache.org/jira/browse/MCOMPILER-496
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Reporter: Tamas Cservenak
> Priority: Major
>
> Hence, it cannot resolve annotation processor from current multi module
> build, and it requires annotation processor to be installed/downloaded.
> Move off from legacy API and use something like maven-artifact-transfer
> instead of maven-compat that delivers Maven2 behaviour.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
