[
https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351111#comment-17351111
]
Dan Berindei commented on MCOMPILER-391:
----------------------------------------
[~rfscholte] what about using the versions from dependency management, is the
fix the same?
We have an annotation processor brought in as a transitive dependency via a BOM.
Some annotation processors (e.g. MapStruct) do not have auto-detection, so
their documentation tells the users to add their AP to
{{<annotationProcessorPaths/>}}. Because that disables auto-detection for all
APs, it means users now have to add our AP there as well, and we'd very much
like to avoid spelling out the AP version (which is definitely not the same as
the BOM version) in the user's POM and in our documentation.
> annotationProcessorPaths have to follow dependencyManagement rules
> ------------------------------------------------------------------
>
> Key: MCOMPILER-391
> URL: https://issues.apache.org/jira/browse/MCOMPILER-391
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Affects Versions: 3.8.0
> Reporter: Stanislav Spiridonov
> Priority: Blocker
> Attachments: MCOMPILER-391.zip
>
>
> # Use the version from dependency management
> # Respect the exclude (blocker for me)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
