[
https://issues.apache.org/jira/browse/MNG-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17745058#comment-17745058
]
Slawomir Jaranowski commented on MNG-7849:
------------------------------------------
if {{server/configuration/..}} is applied for {{WAGON}} and use by it - should
we WARN if user use {{WAGON}} transport?
What do you think to extends {{server}} by something like - without
Xpp3Dom/PlexusConfiguration magic:
{code:xml}
<server>
...
<transport>
<bindAddress/>
<httpHeaders/>
<connectTimeout/>
<requestTimeout/>
<preemptiveAuth/>
</transport>
...
</server>
{code}
it can be documented in XSD and we can add more descriptive warning like:
{noformat}
[WARNING] Settings for server serverId uses legacy format - please use
server/transport
{noformat}
> 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
> 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)
