[
https://issues.apache.org/jira/browse/MNG-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691695#comment-17691695
]
Tamas Cservenak commented on MNG-7663:
--------------------------------------
Sadly, the two APIs are not quite aligned... nor easily adapted. Hence, created
MNG-7706 more to nag Mojo developers to move off from ancient APIs, as it will
pay off for them in future (and will make them able to receive new features
transparently as well).
> The local ArtifactRepository is broken when using enhanced local repo
> ---------------------------------------------------------------------
>
> Key: MNG-7663
> URL: https://issues.apache.org/jira/browse/MNG-7663
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.9.0, 4.0.0-alpha-3
> Reporter: Guillaume Nodet
> Priority: Major
>
> This happens when using split repositories with maven resolver 1.9.x.
> This breaks the flatten-maven-plugin for example.
> The reason is that maven injects a
> {{org.apache.maven.artifact.repository.ArtifactRepository}} instance for the
> {{{}$\{localRepository{}}}} which is the same than the one available from
> {{MavenExecutionRequest.getLocalRepository()}} .
> Unfortunately those objects do not wrap the maven resolver local repository
> implementation and the layout is hardcoded. The actual implementation is
> created by
> [https://github.com/apache/maven/blob/maven-3.9.x/maven-core/src/main/java/org/apache/maven/bridge/MavenRepositorySystem.java#L638]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
