[
https://issues.apache.org/jira/browse/MNG-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700053#comment-17700053
]
Tamas Cservenak commented on MNG-7739:
--------------------------------------
If you have server-wide settings and per-project set Maven version, then yes,
server-wide settings should be "lowest common denominator", that is "old"
method. Here, I'd recommend moving to
{{server/configuration/httpConfiguration/all}} DOM path, as it will work with
both Maven 3.8.x w/ Wagon and Maven 3.9.x w/ native HTTP (but yes, 3.9 will
WARN). Once all projects moved to Maven 3.9.x, upgrade server wide settings and
WARNs are gone.
But am open to other suggestions as well.
> server timeout config in settings.xml is incompatible between 3.8.7 and 3.9.0
> -----------------------------------------------------------------------------
>
> Key: MNG-7739
> URL: https://issues.apache.org/jira/browse/MNG-7739
> Project: Maven
> Issue Type: Bug
> Components: Settings
> Affects Versions: 3.9.0, 4.0.0-alpha-3, 4.0.0-alpha-4
> Reporter: James Z.M. Gao
> Assignee: Tamas Cservenak
> Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-5, 3.9.1
>
>
> resolver in 3.9.0 uses different server configuration for connection timeout
> with wagon in 3.8.7. Now it is not possible to write a correct server
> settings working and clean for both maven versions.
>
> New method with dom path server/configuration/connectTimeout:
> * 3.8.7: exception: Cannot find 'requestTimeout' in class
> org.apache.maven.wagon.providers.http.HttpWagon$__sisu20
> * 3.9.0: works as expected
> Old method with dom path
> server/configuration/httpConfiguration/all/connectionTimeout:
> * 3.8.7: works as expected
> * 3.9.0: works, but warns legacy format
> Old method with dom path
> server/configuration/httpConfiguration/get/connectionTimeout:
> * 3.8.7: works as expected
> * 3.9.0: doesn't work, the configs are ignored
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
