You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2023/07/23 22:48:00 UTC

[jira] [Updated] (MNG-7849) Improvement in settings/server configuration for http transport

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

Slawomir Jaranowski updated MNG-7849:
-------------------------------------
    Component/s: Settings

> Improvement in settings/server configuration for http transport
> ---------------------------------------------------------------
>
>                 Key: MNG-7849
>                 URL: https://issues.apache.org/jira/browse/MNG-7849
>             Project: Maven
>          Issue Type: Improvement
>          Components: Settings
>            Reporter: Slawomir Jaranowski
>            Priority: Major
>
> When we use configuration like: {{server/configuration/httpConfiguration/all/connectionTimeout}} we always have a warning:
> {noformat}
> [WARNING] Settings for server serverId uses legacy format
> {noformat}
> Such warning should be more descriptive.
> Even we use {{-Dmaven.resolver.transport=wagon}} warning is still present - check if should be
> We can also map {{server/configuration/<method>/usePreemptive}} to new value with native transport - many users can use it ... but now don't know that no working any more.
>  
> We can consider if other internal options which support serverId should be mapped in {{server/configuration}}
> We can also consider to extends settings model with transport configuration - instead using 
> {{configuration}} which can be anything and is not validate.



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