This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 83ae91a9 Correct the Wagon providers guide and fix stale links
83ae91a9 is described below

commit 83ae91a93ab808f356627f81447fcca13ff30c45
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Sat Oct 31 21:55:21 2026 +0000

    Correct the Wagon providers guide and fix stale links
    
    Maven 3 and later look up a Wagon by protocol only and drop <wagonProvider> 
from the server configuration, so the Maven 2.2.1 provider selection the guide 
described no longer exists.
---
 .../markdown/guides/mini/guide-http-settings.md    |  2 +-
 .../guides/mini/guide-reproducible-builds.md       |  2 +-
 .../markdown/guides/mini/guide-wagon-providers.md  | 50 ++--------------------
 .../markdown/plugin-developers/plugin-testing.md   |  4 +-
 content/markdown/skins/index.md                    |  4 +-
 5 files changed, 9 insertions(+), 53 deletions(-)

diff --git a/content/markdown/guides/mini/guide-http-settings.md 
b/content/markdown/guides/mini/guide-http-settings.md
index 57906f9e..f18f744a 100644
--- a/content/markdown/guides/mini/guide-http-settings.md
+++ b/content/markdown/guides/mini/guide-http-settings.md
@@ -23,7 +23,7 @@ under the License.
 
 <!-- MACRO{toc} -->
 
-You can use the default wagon implementation for a given protocol, or select 
an alternative wagon provider on a per-protocol basis; see the [Guide to Wagon 
Providers](./guide-wagon-providers.html). With Maven 3.9.0 and later, Wagon is 
used when you select it with `-Dmaven.resolver.transport=wagon`. The native 
HTTP transport reads only the `<all>` block of `httpConfiguration` (`get`, 
`head` and `put` are ignored) and warns about the deprecation, so the 
per-method configuration below appli [...]
+Maven bundles `wagon-http` for HTTP and HTTPS; see the [Guide to Wagon 
Providers](./guide-wagon-providers.html). With Maven 3.9.0 and later, Wagon is 
used when you select it with `-Dmaven.resolver.transport=wagon`. The native 
HTTP transport reads only the `<all>` block of `httpConfiguration` (`get`, 
`head` and `put` are ignored) and warns about the deprecation, so the 
per-method configuration below applies to Wagon only.
 
 This page documents the `<configuration>` block that
 [wagon-http](https://maven.apache.org/wagon/wagon-providers/wagon-http/) reads 
— headers, request parameters,
diff --git a/content/markdown/guides/mini/guide-reproducible-builds.md 
b/content/markdown/guides/mini/guide-reproducible-builds.md
index e400c761..4bc43c5c 100644
--- a/content/markdown/guides/mini/guide-reproducible-builds.md
+++ b/content/markdown/guides/mini/guide-reproducible-builds.md
@@ -192,7 +192,7 @@ For detailed explanations, see [Maven 
"Reproducible/Verifiable Builds" Wiki page
   Details depend on your release process tooling:
 
   - if you use [maven-release-plugin](/plugins/maven-release-plugin/), you'll 
need **version 3.0.0-M1 or later**: it will automatically update the timestamp 
value in `pom.xml` during the release in the same commit that updates version,
-  - if you have a custom release process tooling, you'll need to add the 
feature to your release tooling. Notice that if you're using 
`versions-maven-plugin` in custom release scripts, starting with release 2.9.0, 
[`versions:set` goal updates the 
property](https://github.com/mojohaus/versions-maven-plugin/issues/453).
+  - if you have a custom release process tooling, you'll need to add the 
feature to your release tooling. Notice that if you're using 
`versions-maven-plugin` in custom release scripts, starting with release 2.9.0, 
[`versions:set` goal updates the 
property](https://github.com/mojohaus/versions/issues/453).
   - instead of explicitly writing a timestamp in their `pom.xml`, some people 
tend to prefer using last Git commit timestamp, like `${git.commit.time}` from 
[git-commit-id-maven-plugin](https://github.com/git-commit-id/git-commit-id-maven-plugin)
 (with `<dateFormatTimeZone>UTC</dateFormatTimeZone>` to be independent from 
user's timezone).
 
 Don't hesitate to share your questions or solutions on [user 
mailing-list](/mailing-lists.html).
diff --git a/content/markdown/guides/mini/guide-wagon-providers.md 
b/content/markdown/guides/mini/guide-wagon-providers.md
index 67b3b2d8..bf63f4b4 100644
--- a/content/markdown/guides/mini/guide-wagon-providers.md
+++ b/content/markdown/guides/mini/guide-wagon-providers.md
@@ -19,52 +19,8 @@ under the License.
 
 # Guide to Selecting Alternative Wagon Providers
 
-By default, Maven uses the `java.net.URLConnection` (`HttpURLConnection`) 
classes provided with the JDK to access repositories that use the HTTP/HTTPs 
protocols. Unfortunately, since this implementation contains certain bugs, 
Maven users may find themselves unable to connect to servers that demand some 
configurations. A couple examples of weird behavior include line-wrapping the 
Authorization header's Base64 value when passwords are long, and using cached 
values in preemptive authenticat [...]
+Maven 2.2.1 let you choose between several Wagon implementations for one 
protocol, with the `maven.wagon.provider.<protocol>` property or a 
`<wagonProvider>` element in a `<server>` entry of `settings.xml`. Maven 3 and 
Maven 4 no longer support this: they look up the Wagon by the protocol alone, 
and they remove `<wagonProvider>` from the server configuration before passing 
it on.
 
-Maven 2.2.0 attempted to amend this problem by switching over to a Wagon 
implementation that's based on Apache HttpClient. Unfortunately, it soon became 
apparent that HttpClient doesn't support NTLM (at least, version 2), which 
effectively means users behind NTLMv2 proxies cannot use Maven 2.2.0.
+Maven 3 and Maven 4 bundle two Wagons: `wagon-http`, based on Apache 
HttpClient, for `http` and `https`, and `wagon-file` for `file`. Since Maven 
3.9.0, Maven by default uses the native transports of Maven Resolver for these 
protocols, and Wagon only for the protocols they don't cover or when you select 
it with `-Dmaven.resolver.transport=wagon`. For details, see the [Guide for 
Resolver Transport](./guide-resolver-transport.html).
 
-To hopefully resolve this once and for all, Maven 2.2.1 will contain support 
for specifying which Wagon provider you want to use for a given protocol during 
the build. The provider name will then be appended to the protocol using the 
format `<protocol>-<provider>` to form the component role-hint for the Wagon.
-
-As of Maven 2.2.1, there are two ways to specify which Wagon provider should 
be used: via the command line, or in the `<server>` configuration section of 
the `settings.xml`.
-
-## Command-Line Configuration
-
-To specify the Wagon provider from the command line, simply use the 
`-Dmaven.wagon.provider.<protocol>=<provider-name>` command-line option, like 
the following:
-
-```
-mvn -Dmaven.wagon.provider.http=httpclient clean install
-```
-
-This instructs Maven to use the HttpClient-based Wagon implementation for 
connections to HTTP repositories.
-
-## `settings.xml` Configuration
-
-To specify which Wagon provider to use for a particular server, modify your 
`settings.xml` file to add the `<wagonProvider>` configuration to your 
`<server>` entry, like the following:
-
-```xml
-<settings>
-  [...]
-  <servers>
-    <server>
-      <id>central</id>
-      <configuration>
-        <wagonProvider>httpclient</wagonProvider>
-        [...]
-      </configuration>
-    </server>
-```
-
-## Available Wagon Providers
-
-Maven 2.2.1 provides two providers for HTTP/HTTPS Wagons: `lightweight` and 
`httpclient`. If you add a new HTTP Wagon implementation via build extension, 
you'll need to make sure the extension binds its Wagon components to role-hints 
of the form `<protocol>-<provider>` in order to allow users to specify your 
alternative Wagon provider. For instance, the HttpClient HTTP Wagon component 
definition looks like this:
-
-```xml
-<component>
-  <role>org.apache.maven.wagon.Wagon</role>
-  <role-hint>http-httpclient</role-hint>
-  
<implementation>org.apache.maven.wagon.providers.http.HttpWagon</implementation>
-  <instantiation-strategy>per-lookup</instantiation-strategy>
-</component>
-```
-
-**NOTE:** The default provider for HTTP/HTTPS Wagons is `lightweight`.
+Wagons for other protocols, such as `wagon-ftp` or `wagon-ssh-external`, are 
added to the build as build extensions; see [Deploying over HTTP, FTP and 
SSH](./guide-deployment-transports.html). For the configuration that 
`wagon-http` reads, see [Advanced configuration to HttpClient HTTP 
Wagon](./guide-http-settings.html).
diff --git a/content/markdown/plugin-developers/plugin-testing.md 
b/content/markdown/plugin-developers/plugin-testing.md
index 272859a1..d94eab0e 100644
--- a/content/markdown/plugin-developers/plugin-testing.md
+++ b/content/markdown/plugin-developers/plugin-testing.md
@@ -158,7 +158,7 @@ maven-verifier is retired, and 2.0.0 is its final release. 
Existing tests keep w
 
 You can use 
[maven-invoker-plugin](https://maven.apache.org/plugins/maven-invoker-plugin/) 
to invoke Maven and to provide some BeanShell/Groovy tests. Tests written in 
this way don't run under JUnit/TestNG; instead, they're run by Maven itself.
 
-You can take a look at the 
[maven-install-plugin](https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-install-plugin/src/it/)
 to see how integration tests are written.
+You can take a look at the 
[maven-install-plugin](https://github.com/apache/maven-install-plugin/tree/master/src/it)
 to see how integration tests are written.
 
 ```xml
 <project xmlns="http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
@@ -169,7 +169,7 @@ You can take a look at the 
[maven-install-plugin](https://svn.apache.org/repos/a
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-invoker-plugin</artifactId>
-        <version>3.9.1</version>
+        <version>3.10.1</version>
         <configuration>
           <projectsDirectory>src/it</projectsDirectory>
           <pomIncludes>
diff --git a/content/markdown/skins/index.md b/content/markdown/skins/index.md
index 954b9a59..2c555df3 100644
--- a/content/markdown/skins/index.md
+++ b/content/markdown/skins/index.md
@@ -27,8 +27,8 @@ The following table lists skins that are available for you to 
use in your Maven
 
 | **Skin**                                          | **Version** | Site 
Plugin Version | **Description**              | **Source Repository**           
                                                                                
          | **Issue Tracking**                                                  
|
 
|:--------------------------------------------------|:------------|:--------------------|:-----------------------------|:--------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------------------|
-| [ `Maven Fluido Skin`](/skins/maven-fluido-skin/) | 2.1.0       | [3.21.0,)  
         | Skin based on Bootstrap CSS. | 
[Git](http://gitbox.apache.org/repos/asf/maven-fluido-skin.git) / 
[GitHub](https://github.com/apache/maven-fluido-skin/)  | [GitHub 
Issues](https://github.com/apache/maven-fluido-skin/issues) |
-| [ `Maven Fluido Skin`](/skins/maven-fluido-skin/) | 1.12.0      | 
[3.10.0,3.20.0)     | Skin based on Bootstrap CSS. | 
[Git](http://gitbox.apache.org/repos/asf/maven-fluido-skin.git/) / 
[GitHub](https://github.com/apache/maven-fluido-skin/) | [GitHub 
Issues](https://github.com/apache/maven-fluido-skin/issues) |
+| [ `Maven Fluido Skin`](/skins/maven-fluido-skin/) | 2.1.0       | [3.21.0,)  
         | Skin based on Bootstrap CSS. | 
[Git](https://gitbox.apache.org/repos/asf/maven-fluido-skin.git) / 
[GitHub](https://github.com/apache/maven-fluido-skin/)  | [GitHub 
Issues](https://github.com/apache/maven-fluido-skin/issues) |
+| [ `Maven Fluido Skin`](/skins/maven-fluido-skin/) | 1.12.0      | 
[3.10.0,3.20.0)     | Skin based on Bootstrap CSS. | 
[Git](https://gitbox.apache.org/repos/asf/maven-fluido-skin.git) / 
[GitHub](https://github.com/apache/maven-fluido-skin/) | [GitHub 
Issues](https://github.com/apache/maven-fluido-skin/issues) |
 
 ### Retired
 

Reply via email to