[
https://issues.apache.org/jira/browse/MRESOLVER-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527468#comment-17527468
]
Hudson commented on MRESOLVER-253:
----------------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » master #26
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/26/
> 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 "prefix"
> from from path prefix composer. Default behavior is not changed (will not use
> prefix, local repository will work as before).
> The point in change is that it introduce a "composer", that is composing LRM
> path prefixes, and is able to apply different strategies, and split local
> repository into "installed" (locally built and installed) and "cached"
> (downloaded from remote), etc.
> There are several composer options out of the box:
> * split between "cached" and locally "installed" artifacts
> * split "cached" artifacts based on their origin (remote repository)
> * split between "release" and "snapshot" versioned artifacts
> These properties can all be configured via resolver "configuration",
> essentially via session configuration.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
