[
https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803209#comment-17803209
]
ASF GitHub Bot commented on MCOMPILER-391:
------------------------------------------
famod commented on PR #180:
URL:
https://github.com/apache/maven-compiler-plugin/pull/180#issuecomment-1877280262
> I think the missing relocation warning has the same cause - the plugin (or
more precisely the dependency resolution mechanism the plugin uses) simply does
not know that the artifact was relocated, because without version, it cannot
fetch the relocation config.
>
> I believe the relocation warning gets printed in case you depend on the
old artifact, but the version must be known, explicitly or via depMgmt: e.g:
>
> ```
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-jpamodelgen</artifactId>
> <verison>6.0.0</version>
> ```
>
> In that case, the POM is fetched, relocation config found and the warning
can be printed.
I guess I should have been more precise:
I had exactly that (only a version property instead of the version literal,
but that shouldn't make any difference) and still no warning. Maven 3.9.6, btw.
> 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
> Assignee: Slawomir Jaranowski
> Priority: Blocker
> Fix For: 3.12.0
>
> Attachments: MCOMPILER-391.zip
>
>
> # Use the version from dependency management
> # Respect the exclude (blocker for me)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
