[
https://issues.apache.org/jira/browse/MNG-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737241#comment-17737241
]
Tamas Cservenak commented on MNG-6877:
--------------------------------------
Even first mvn package works as well, hence, apt processor IS resolved from
workspace.
My local changes:
* using m-compiler-p 3.11.0 (not the one from reproducer)
* declared dependency apt -> apt-processor
Now, this 2nd change fixes the ordering (as originally it wanted to build apt
(which uses apt-processor) before apt-processor => fail. This dependency is a
must for proper topological sort of projects (to get right order), but can be
made optional for example.
> 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)
