[
https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803039#comment-17803039
]
ASF GitHub Bot commented on MCOMPILER-391:
------------------------------------------
psiroky commented on PR #180:
URL:
https://github.com/apache/maven-compiler-plugin/pull/180#issuecomment-1876984635
@famod thanks. In this case, I am not quite sure this is supported from
Maven itself.
I assume there is no version anywhere in the project depMgmt for
`org.hibernate:hibernate-jpamodelgen` and so there is also no information which
could map it to the new artifact `org.hibernate.orm:hibernate-jpamodelgen`.
That mapping information is part of the old / original POM, but since the
plugin does not have the version for this old artifact, it cannot lookup the
POM with the relocation config.
Does that make sense? Or am I overlooking something in the setup?
Or this perhaps something that is working for you outside of the compiler
plugin configuration with standard project dependencies?
> 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)
