This is an automated email from the ASF dual-hosted git repository. cstamas pushed a commit to branch transport-doco-update in repository https://gitbox.apache.org/repos/asf/maven-site.git
commit e1b6fd576a42c9a6d61f094906df7531c3970448 Author: Tamas Cservenak <[email protected]> AuthorDate: Tue Mar 7 09:09:26 2023 +0100 Call things what they are (not "resolver transport" but Wagon) and create new page that is about "resolver transport". --- content/apt/guides/mini/guide-http-settings.apt | 14 +++++----- .../guides/mini/guide-resolver-transport.md | 30 ++++++++++++++++++++++ 2 files changed, 38 insertions(+), 6 deletions(-) diff --git a/content/apt/guides/mini/guide-http-settings.apt b/content/apt/guides/mini/guide-http-settings.apt index 64634ba2..98a55304 100644 --- a/content/apt/guides/mini/guide-http-settings.apt +++ b/content/apt/guides/mini/guide-http-settings.apt @@ -26,22 +26,24 @@ ~~ NOTE: For help with the syntax of this file, see: ~~ http://maven.apache.org/doxia/references/apt-format.html -Advanced Configuration of the Maven Resolver Transport - -%{toc} +Advanced Configuration of the Maven Wagon Transport You can use the default transport for a given protocol, or you can select the transport you want by using the configuration. For more information about existing Resolver transports see the {{{https://maven.apache.org/resolver/} Resolver}} site. The default transport in Maven 3.x is Transport-Wagon, the Wagon layer having been introduced in Maven 2.x. Since then, more modern transports were introduced as well, even supporting overlapping protocols. The default - transport in Maven 4.x changed to the more modern + transport in Maven 3.9.x changed to the more modern {{{https://maven.apache.org/resolver/maven-resolver-transport-http/index.html}"native"; HTTP}} transport. Ultimate reference for resolver transport configuration can be found on - {{{https://maven.apache.org/resolver/configuration.html} this page}}. While one can easily define simple typed + {{{https://maven.apache.org/resolver/configuration.html} configuration}} page. While one can easily define simple typed values on command line using <<<-D...>>> switch, some more complex values, like HTTP headers, cannot. -*Advanced configuration to Transports + The resolver transport {{{./guide-resolver-transport.html}guide is here}}. + +%{toc} + +*Advanced configuration to Wagon Using your <<<settings.xml>>> you can customize the transport configurations in several ways. diff --git a/content/markdown/guides/mini/guide-resolver-transport.md b/content/markdown/guides/mini/guide-resolver-transport.md new file mode 100644 index 00000000..49a2f820 --- /dev/null +++ b/content/markdown/guides/mini/guide-resolver-transport.md @@ -0,0 +1,30 @@ +## Guide for Resolver Transport +<!-- +Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. +--> + +Starting with Maven 3.9.0 release, the "default transport" (the default transport used by Maven Resolver) +changed from ancient Wagon to modern resolver "native HTTP" transport. + +## Switching between transports + +The transport used by resolver can be controlled using `-Dmaven.resolver.transport` user property, where accepted +values are `native` (the default), `wagon` (falls back to legacy Wagon) and `auto` (delegates to resolver to sort +out defaults). + +TBD \ No newline at end of file
