[ 
https://issues.apache.org/jira/browse/MRESOLVER-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tamas Cservenak updated MRESOLVER-440:
--------------------------------------
    Description: 
Currently ApacheHC transport is called "http" while JDK transport is called 
"jdk" and JettyHC is "jetty". Also, historically all transports were 
connectors, and later was "basic" connector added and transports introduced, 
but many transport related configuration properties remained as "connector".

Proposed changes:
 * Rename ApacheHC to "apache" transport, to "free" the "http" config key. 
There will be no "http" transport anymore, it is reserved for "shared HTTP 
related config" that is shared among multiple HTTP transports (apache, jdk, 
jetty...).
 * Rename transport specific configurations from "aether.connector.apache..." 
and "aether.connector.jdk..." to their proper names "aether.transport..."
 * keep "aether.transport.http..." for generic HTTP protocol related 
configuration (that may be used by all HTTP using transports).
 * align many other (for historical reason) badly keyed property to "proper 
place".
 * sort out documentation for these, ideally the page should be generated

  was:
Currently ApacheHC transport is called "http" while JDK transport is called 
"jdk" and JettyHC is "jetty". Also, historically all transports were 
connectors, and later was "basic" connector added and transports introduced, 
but many transport related configuration properties remained as "connector".

Proposed changes:
 * Rename ApacheHC to "apache" transport, to "free" the "http" config key. 
There will be no "http" transport anymore, it is reserved for "shared HTTP 
related config" that is shared among multiple HTTP transports (apache, jdk, 
jetty...).
 * Rename transport specific configurations from "aether.connector.apache..." 
and "aether.connector.jdk..." to their proper names "aether.transport..."
 * keep "aether.transport.http..." for generic HTTP protocol related 
configuration (that may be used by all HTTP using transports).
 * align many other (for historical reason) badly keyed property to "proper 
place".


> Clean up transport names, configuration properties and documentation
> --------------------------------------------------------------------
>
>                 Key: MRESOLVER-440
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-440
>             Project: Maven Resolver
>          Issue Type: Task
>          Components: Resolver
>            Reporter: Tamas Cservenak
>            Assignee: Tamas Cservenak
>            Priority: Major
>             Fix For: 2.0.0
>
>
> Currently ApacheHC transport is called "http" while JDK transport is called 
> "jdk" and JettyHC is "jetty". Also, historically all transports were 
> connectors, and later was "basic" connector added and transports introduced, 
> but many transport related configuration properties remained as "connector".
> Proposed changes:
>  * Rename ApacheHC to "apache" transport, to "free" the "http" config key. 
> There will be no "http" transport anymore, it is reserved for "shared HTTP 
> related config" that is shared among multiple HTTP transports (apache, jdk, 
> jetty...).
>  * Rename transport specific configurations from "aether.connector.apache..." 
> and "aether.connector.jdk..." to their proper names "aether.transport..."
>  * keep "aether.transport.http..." for generic HTTP protocol related 
> configuration (that may be used by all HTTP using transports).
>  * align many other (for historical reason) badly keyed property to "proper 
> place".
>  * sort out documentation for these, ideally the page should be generated



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to