[
https://issues.apache.org/jira/browse/MRESOLVER-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-585:
--------------------------------------
Description:
We have a bit of chicken-and-egg problem here, as LocalRepositoryManager is
created by system and one needs session for it, but session cannot be created
without LocalRepositoryManager.
Session Builder provides "workaround" in form of withXXX methods, but those all
cannot use custom LocalRepositoryManager...
In short: this method is "special". The usual way to use custom LRM is to
integrate it with LRMProvider and tune it with priorities and/or custom
LocalReposirory type strings...
was:
We have a bit of chicken-and-egg problem here, as LocalRepositoryManager is
created by system and one needs session for it, but session cannot be created
without LocalRepositoryManager.
Session Builder provides "workaround" in form of withXXX methods, but those all
cannot use custom LocalRepositoryManager...
> Is unclear how to use custom LocalRepositoryManager with builder
> ----------------------------------------------------------------
>
> Key: MRESOLVER-585
> URL: https://issues.apache.org/jira/browse/MRESOLVER-585
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
> Affects Versions: 2.0.0
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.1
>
>
> We have a bit of chicken-and-egg problem here, as LocalRepositoryManager is
> created by system and one needs session for it, but session cannot be created
> without LocalRepositoryManager.
> Session Builder provides "workaround" in form of withXXX methods, but those
> all cannot use custom LocalRepositoryManager...
> In short: this method is "special". The usual way to use custom LRM is to
> integrate it with LRMProvider and tune it with priorities and/or custom
> LocalReposirory type strings...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
