[jira] [Commented] (MRESOLVER-440) Clean up transport names, configuration properties and documentation

2023-11-28 Thread ASF GitHub Bot (Jira)


[ 
https://issues.apache.org/jira/browse/MRESOLVER-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790597#comment-17790597
 ] 

ASF GitHub Bot commented on MRESOLVER-440:
--

cstamas merged PR #382:
URL: https://github.com/apache/maven-resolver/pull/382




> 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, 2.0.0-alpha-3
>
>
> 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
> As part of this work along with source changes (mostly javadoc) a "tool" has 
> been made that auto-generates this page 
> https://maven.apache.org/resolver/configuration.html



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


[jira] [Commented] (MRESOLVER-440) Clean up transport names, configuration properties and documentation

2023-11-28 Thread ASF GitHub Bot (Jira)


[ 
https://issues.apache.org/jira/browse/MRESOLVER-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790594#comment-17790594
 ] 

ASF GitHub Bot commented on MRESOLVER-440:
--

cstamas opened a new pull request, #382:
URL: https://github.com/apache/maven-resolver/pull/382

   Seems the "atypical" modules like supplier and
   demo snippets were completely omitted from the
   transport rename, and were still using renamed
   transport-http instead the new transport-apache.
   
   ---
   
   https://issues.apache.org/jira/browse/MRESOLVER-440




> 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, 2.0.0-alpha-3
>
>
> 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
> As part of this work along with source changes (mostly javadoc) a "tool" has 
> been made that auto-generates this page 
> https://maven.apache.org/resolver/configuration.html



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


[jira] [Commented] (MRESOLVER-440) Clean up transport names, configuration properties and documentation

2023-11-26 Thread Tamas Cservenak (Jira)


[ 
https://issues.apache.org/jira/browse/MRESOLVER-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789810#comment-17789810
 ] 

Tamas Cservenak commented on MRESOLVER-440:
---

Almost all solved, only generated "description" may need a bit more love, but 
we can sort out that "on the go"

> 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
> As part of this work along with source changes (mostly javadoc) a "tool" has 
> been made that auto-generates this page 
> https://maven.apache.org/resolver/configuration.html



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


[jira] [Commented] (MRESOLVER-440) Clean up transport names, configuration properties and documentation

2023-11-26 Thread ASF GitHub Bot (Jira)


[ 
https://issues.apache.org/jira/browse/MRESOLVER-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789809#comment-17789809
 ] 

ASF GitHub Bot commented on MRESOLVER-440:
--

cstamas merged PR #375:
URL: https://github.com/apache/maven-resolver/pull/375




> 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
> As part of this work along with source changes (mostly javadoc) a "tool" has 
> been made that auto-generates this page 
> https://maven.apache.org/resolver/configuration.html



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