You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (Jira)" <ji...@apache.org> on 2020/03/29 17:40:00 UTC
[jira] [Commented] (MNG-6877) Separate scope for annotation
processing
[ https://issues.apache.org/jira/browse/MNG-6877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17070450#comment-17070450 ]
Karl Heinz Marbaise commented on MNG-6877:
------------------------------------------
Can you provide a full working 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.3.4#803005)