[
https://issues.apache.org/jira/browse/MRESOLVER-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-425:
--------------------------------------
Description:
This is just an idea, but: maybe RepositorySystemSession should carry
VersionScheme as well? Currently Maven defines it as "component" (see
MNG-7103), while IMHO a more "flexible" way to manage version schemes are
needed.
But again, resolver really does not use version scheme, merely dependencyFilter
ctors accept it only...
was:
This is just an idea, but: maybe RepositorySystemSession should carry
VersionScheme as well? Currently Maven defines it as "component" (see
MNG-7103), while IMHO a more "flexible" way to manage version schemes are
needed.
But again, resolver really does not use version scheme, merely
dependencyFilters accept it only...
> Session should carry VersionScheme?
> -----------------------------------
>
> Key: MRESOLVER-425
> URL: https://issues.apache.org/jira/browse/MRESOLVER-425
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0
>
>
> This is just an idea, but: maybe RepositorySystemSession should carry
> VersionScheme as well? Currently Maven defines it as "component" (see
> MNG-7103), while IMHO a more "flexible" way to manage version schemes are
> needed.
> But again, resolver really does not use version scheme, merely
> dependencyFilter ctors accept it only...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
