[
https://issues.apache.org/jira/browse/MCOMPILER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17803175#comment-17803175
]
ASF GitHub Bot commented on MCOMPILER-391:
------------------------------------------
famod commented on PR #180:
URL:
https://github.com/apache/maven-compiler-plugin/pull/180#issuecomment-1877127524
@psiroky
Yeah, I think you have a very valid point: There is no explicit version for
that old groupId and so there is no precise way to find the exact pom with the
relocation info (=> new groupId).
As a human you could just check the latest version for the old groupId and
get the relocation info from that but I doubt there is a nice way of finding
the latest version via Maven builtin features (?).
Not worth the hassle.
For extra user-friendliness this plugin could check (if no version is found)
for _similar_ deps, e.g. same artifactId but differen groupId and print put all
those candidates, but relocations are not limited to groupIds (AFAIK), so...
It probably boils down to the question why there are/were no relocations
warnings like you get for "normal" dependencies. For general plugin
dependencies that's clearly something that Maven should cover.
`annotationProcessorPaths` is probably a different story.
> 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)
