[
https://issues.apache.org/jira/browse/MRESOLVER-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-266:
--------------------------------------
Description:
Rework how named lock factory adapter is created, it is the ONLY bit reaching
directly to Java System Properties instead to rely on session config
properties. This makes it impossible to control from Maven for example (as it
is "too late").
Proposed changes:
* adapter should be created based on -session- config properties, not Java
system properties
* adapter should be stored within session
* adapter creation should be vastly simplified (currently we have 4 involved
class: selectors and default sync context)
was:
Rework how named lock factory adapter is created, it is the ONLY bit reaching
directly to Java System Properties instead to rely on session config
properties. This makes it impossible to control from Maven for example (as it
is "too late").
Proposed changes:
* adapter should be created based on session config properties, not Java system
properties
* adapter should be stored within session
* adapter creation should be vastly simplified (currently we have 4 involved
class: selectors and default sync context)
> Simplify adapter creation and align configuration for it
> --------------------------------------------------------
>
> Key: MRESOLVER-266
> URL: https://issues.apache.org/jira/browse/MRESOLVER-266
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 1.9.0
>
>
> Rework how named lock factory adapter is created, it is the ONLY bit reaching
> directly to Java System Properties instead to rely on session config
> properties. This makes it impossible to control from Maven for example (as it
> is "too late").
> Proposed changes:
> * adapter should be created based on -session- config properties, not Java
> system properties
> * adapter should be stored within session
> * adapter creation should be vastly simplified (currently we have 4 involved
> class: selectors and default sync context)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
