[jira] [Commented] (MRESOLVER-310) Preserve configuration of Enhanced LRM in local repo

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MRESOLVER-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689366#comment-17689366 ] 

ASF GitHub Bot commented on MRESOLVER-310:
------------------------------------------

slawekjaranowski opened a new pull request, #248:
URL: https://github.com/apache/maven-resolver/pull/248

   Proposition for  https://issues.apache.org/jira/browse/MRESOLVER-310
   
   TODO:
   - discover, think out if all parameters should be immutable and preserved during repo created 
   - move rest of config parameters
   - add unit test 




> Preserve configuration of Enhanced LRM in local repo
> ----------------------------------------------------
>
>                 Key: MRESOLVER-310
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-310
>             Project: Maven Resolver
>          Issue Type: Improvement
>            Reporter: Slawomir Jaranowski
>            Priority: Major
>
> We can configure  {{Enhanced LRM}} with options like {{Split Local Repository}} which change local repo layout.
> Eg.
>  - local repo is created by main Maven process and I want to use this repo as is or with CLRM with IT test, IT tests have sanboxes environment with own Maven settings ... so artifacts in {{outer}} / {{tail}} repo will be not found because layout of local repo is wrong interpreted.
> Next case
>  - when we change configuration on LRM, new paths will be used and old items will remains in forgotten locations
> Proposition:
>  - create and store LRM configuration in repo and when configuration exist use is as primary
>  - when current session has a configuration which is different from stored in repo inform user by warn that should simply remove/clean repo to take new configuration on place.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)