[MRESOLVER-310] Preserve configuration of Enhanced LRM in local repo

[jira-importer]

Slawomir Jaranowski opened MRESOLVER-310 and commented

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.

---

Issue Links:

• MRESOLVER-163 Introduce "configuration" or "feature" helper to centralize various flags/params/configs

Remote Links:

• GitHub Pull Request #248
  

[jira-importer]

Tamas Cservenak commented

To me this looks related to MRESOLVER-163.

[jira-importer]

Slawomir Jaranowski commented

It is different than 163 - in this issue we need / should preserver configuration for LRM in case to know which configuration was used during initialization given LRM.

Yes I know we can have many corner cases.

But we can start working on 163 and next extend it for this issue.