[
https://issues.apache.org/jira/browse/MRESOLVER-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637633#comment-17637633
]
ASF GitHub Bot commented on MRESOLVER-297:
------------------------------------------
cstamas merged PR #223:
URL: https://github.com/apache/maven-resolver/pull/223
> Chained LRM
> -----------
>
> Key: MRESOLVER-297
> URL: https://issues.apache.org/jira/browse/MRESOLVER-297
> Project: Maven Resolver
> Issue Type: New Feature
> Components: Resolver
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 1.9.2
>
>
> Implement "chained" LRM. This utility would NOT meant to be used in any
> production env, but rather in some confined use cases like "isolated"
> environment like running IT tests.
> If you split "inner" and "outer" build when for example running Maven IT
> Suite, the "outer" build is directly affected by user setup (user
> settings.xml and other things), while "inner" is (should be) isolated.
> Moreover, the "outer" build builds plugins and dependencies that are required
> by "inner" build. Simply sharing same local repository does not work, see for
> example MNG-5185 but it boils down to this:
> * Maven3 enhanced local repo tracks "artifact availability", by repo ID and
> this is affected by user env (ie. MRM being used with own repo ID)
> * inner IT build has central repo "shut down" (file/null), as it expects all
> resolved and present in local repo by "outer" build
> * while this is true (files are present) they may be not available, as
> "outer" build user env may use different settings than inner (ie. a MRM with
> own repo ID)
> The implemented "chained" LRM can isolate local repo for ITs:
> * sandbox "inner" build ITs into own local repo
> * but allow artifact resolution from local repo used by "outer" build
> * this 2nd is needed as dependencies and artifacts resolved and installed by
> "outer" build and are needed in "inner" build
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
