[
https://issues.apache.org/jira/browse/MNG-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737215#comment-17737215
]
Tomas Langer edited comment on MNG-6877 at 6/26/23 3:58 PM:
------------------------------------------------------------
Is there a chance this will be resolved?
We have the same problem in project Helidon
([https://github.com/helidon-io/helidon),] and right now this causes a lot of
problems:
* we cannot build in parallel (such as when using Maven daemon)
* we are forced to duplicate annotation processor dependencies as `optional`
dependencies, which may bring in wrong dependencies for a module for the sole
purpose of fixing the reactor order
* we are forced to use an explicit version of our own annotation processor
that is within the same project and has dependency management section correctly
defined
As our annotation processors use common classes, and we use the "mono-repo"
approach with a single project, this is quite a heavy disadvantage, as we
cannot remove them to another project...
I would expect that annotation processor paths honor dependency management of
the project, and that reactor orders the modules with this in mind as well...
(currently on Maven 3.9.1)
was (Author: tomas.langer):
Is there a chance this will be resolved?
We have the same problem in project Helidon
([https://github.com/helidon-io/helidon),] and right now this causes a lot of
problems:
* we cannot build in parallel (such as when using Maven daemon)
* we are forced to duplicate annotation processor dependencies as `optional`
dependencies, which may bring in wrong dependencies for a module for the sole
purpose of fixing the reactor order
* we are forced to use an explicit version of our own annotation processor
that is within the same project and has dependency management section correctly
defined
As our annotation processors use common classes, and we use the "mono-repo"
approach with a single project, this is quite a heavy disadvantage, as we
cannot remove them to another project...
I would expect that annotation processor paths honor dependency management of
the project, and that reactor orders the modules with this in mind as well...
> 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)
