[
https://issues.apache.org/jira/browse/MRESOLVER-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamás Cservenák updated MRESOLVER-253:
--------------------------------------
Issue Type: New Feature (was: Task)
> Dynamic prefixes for LRM
> ------------------------
>
> Key: MRESOLVER-253
> URL: https://issues.apache.org/jira/browse/MRESOLVER-253
> Project: Maven Resolver
> Issue Type: New Feature
> Components: Resolver
> Reporter: Tamás Cservenák
> Assignee: Tamás Cservenák
> Priority: Major
> Fix For: 1.8.1
>
>
> Enhances existing "enhanced" LRM (local repository manager) with "dynamic
> prefix". Default behaviour is not changed (uses NOOP composer).
> The point in change is that it introduces a "composer", that is composing LRM
> path prefix, and is able to apply different strategies, and split local
> repository into "local" (locally built and installed) and "remote"
> (downloaded from remote, cache really), etc.
> There are 3 composers, but they are extensible (just implement new
> `DynamicLocalRepositoryManagerFactory` component):
> * `noop` - makes enhanced LRM behave exactly same as before, this is the
> default composer.
> * `split` - splits by local and remote release/snapshot
> * `split-repository` - as split but factors in remote repoId as well,
> basically splits cache by origin
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
