[
https://issues.apache.org/jira/browse/MNG-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737655#comment-17737655
]
Tomas Langer commented on MNG-6877:
-----------------------------------
That is also not correct, is it? Plugin dependencies are to extend the features
of the plugin, not to add annotations processors.
If that is a workaround for the reactor ordering, then I get it, and we can use
it. But I do not see that as a solution of the problem
> Separate scope for annotation processing
> ----------------------------------------
>
> Key: MNG-6877
> URL: https://issues.apache.org/jira/browse/MNG-6877
> Project: Maven
> Issue Type: New Feature
> Components: Dependencies
> Affects Versions: 3.6.3
> Reporter: Stanislav Spiridonov
> Priority: Major
>
> Hi, I know about annotationProcessorPaths of maven-compiler-plugin and it
> works somehow, but with some limitations
> # dependencyManagement does not work for path elements (need to specify
> version). workaround use variable
> # if I have apt-processor as a part of the project (separate module) and use
> it only in the maven-compiler-plugin configuration it has been built in the
> last order, that brakes build
> # the maven-compiler-plugin can use only INSTALLED artifacts, not from a
> reactor
>
> Use the processor as a usual dependency is also not a case (even with
> provided scope)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
