[
https://issues.apache.org/jira/browse/MNG-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737244#comment-17737244
]
Tomas Langer commented on MNG-6877:
-----------------------------------
The thing is that the dependency on apt-processor should not be explicitly
defined in `dependencies`, unless there is a new scope, which makes it clear
that the APT is NOT on classpath of the application for compilation, but only
on APT classapth of the compiler.
This is a huge difference that is important, especially when using modularized
(JPMS) modules and processors.
> 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)
