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 e399db52 Keep the old section anchors of three rewritten guides
e399db52 is described below
commit e399db5281fa334a29de72f10883e59ab7f6fc59
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Sun Nov 1 10:32:47 2026 +0000
Keep the old section anchors of three rewritten guides
The HTTP settings, Wagon providers and creating archetypes guides were
rewritten or renumbered, which dropped 17 section ids that published pages and
bookmarks link to. Each old id now sits on the section that holds its content;
do not remove them as unused.
---
.../guides/mini/guide-creating-archetypes.md | 2 ++
.../markdown/guides/mini/guide-http-settings.md | 24 ++++++++++++++++++++++
.../markdown/guides/mini/guide-wagon-providers.md | 5 +++++
3 files changed, 31 insertions(+)
diff --git a/content/markdown/guides/mini/guide-creating-archetypes.md
b/content/markdown/guides/mini/guide-creating-archetypes.md
index da0f6b87..5ef5ea1c 100644
--- a/content/markdown/guides/mini/guide-creating-archetypes.md
+++ b/content/markdown/guides/mini/guide-creating-archetypes.md
@@ -162,6 +162,8 @@ The `junit-bom` import in `dependencyManagement` sets the
version of every JUnit
Before you install the archetype, add at least one integration test. Each test
is a directory in `src/test/resources/projects/` of the archetype project,
containing an `archetype.properties` file with the values for the generation
and a `goal.txt` file with the Maven goals to run in the generated project. It
can also contain a `reference/` directory with the expected project, and a
`verify.groovy` script. The `archetype:integration-test` goal, which the
`maven-archetype` packaging runs d [...]
+<a id="a4._Install_the_archetype_and_run_the_archetype_plugin"></a>
+
## 5. Install the archetype and run the archetype plugin
Now you are ready to install the archetype:
diff --git a/content/markdown/guides/mini/guide-http-settings.md
b/content/markdown/guides/mini/guide-http-settings.md
index f18f744a..aef2b88b 100644
--- a/content/markdown/guides/mini/guide-http-settings.md
+++ b/content/markdown/guides/mini/guide-http-settings.md
@@ -19,6 +19,8 @@ under the License.
# Advanced configuration to HttpClient HTTP Wagon
+<a id="Introduction"></a>
+
**This page contains Wagon specific information, but the default transport in
Maven 3.9.0+ is NOT Wagon anymore. Make sure to check the [Resolver Transport
guide](./guide-resolver-transport.html) first, as things have changed.**
<!-- MACRO{toc} -->
@@ -41,6 +43,8 @@ different implementation built on
`java.net.HttpURLConnection`.
Settings that are global rather than per-server are exposed as system
properties
instead; see [System properties](#System_properties) at the end.
+<a id="The_Basics"></a>
+
## Where configuration goes
In a Maven build, per-server configuration lives in `settings.xml`, inside the
@@ -67,6 +71,9 @@ provider class. Programmatically the same settings are the
`setHttpConfiguration
`setHttpHeaders`, `setBasicAuthScope`, `setProxyBasicAuthScope` and
`setInitialBackoffSeconds` methods of `AbstractHttpClientWagon`.
+<a id="Configuring_GET.2C_HEAD.2C_PUT.2C_or_All_of_the_Above"></a>
+<a id="Read_time_out"></a>
+
## `httpConfiguration`
`httpConfiguration` is the main entry point. It is an
@@ -144,6 +151,8 @@ method block and leave `<all>` out. This is what
`HttpWagonPreemptiveTest` does — it configures nothing but
`setAll(new HttpMethodConfiguration().setUsePreemptive(true))`.
+<a id="Non-String_Parameter_Values"></a>
+
### Writing `headers` and `params`
Both are `java.util.Properties`, and Plexus accepts two spellings for those.
The
@@ -171,6 +180,8 @@ Use the long form for keys that are not valid XML element
names — most of the
keys below contain dots, which is fine, but nothing stops a header name from
containing characters that are not.
+<a id="Taking_Control_of_Your_HTTP_Headers"></a>
+
### `headers`
Headers from the configuration are applied with `setHeader`, so they replace
any
@@ -192,6 +203,8 @@ Pragma: no-cache
before your own headers are applied. Set it to `false` to suppress them.
+<a id="Fine-Tuning_HttpClient_Parameters"></a>
+
### `params`
`<params>` is an escape hatch onto HttpClient's `RequestConfig`. Only the keys
below
@@ -230,6 +243,8 @@ applied, so `http.protocol.cookie-policy` overrides that
default.
are applied; `http.protocol.expect-continue` can therefore turn it off. It is
deliberately not enabled for `MKCOL`, which has no body.
+<a id="Ignoring_Cookies"></a>
+
### Ignoring cookies
Some repositories send session cookies, often by mistake, alongside HTTP
redirection. The
@@ -274,6 +289,8 @@ tried.
always `UsernamePasswordCredentials`, never `NTCredentials`, so the registered
NTLM
scheme has nothing usable to offer. NTLM is only wired up for proxies — see
below.
+<a id="Example.3A_Using_Preemptive_Authentication"></a>
+
### Preemptive authentication
By default HttpClient waits for a `401` challenge before sending credentials.
With
@@ -305,6 +322,8 @@ Preemptive Basic authentication is only ever Basic — the
cache entry is a
source marks this as a known wart ("FIXME Perform only when preemptive has been
configured").
+<a
id="Example.3A_Lifting_auth_scope_restriction_for_external_authentication_systems"></a>
+
### `basicAuth` and `proxyAuth` — overriding the authentication scope
By default the `AuthScope` for the target is built from the repository's own
host and
@@ -375,6 +394,9 @@ provider does with them:
exist, a `BasicScheme` with `ChallengeState.PROXY` is put in the `AuthCache`
for the
proxy host.
+<a id="Support_for_General-Wagon_Configuration_Standards"></a>
+<a id="Connection_Timeouts"></a>
+
## Connection timeout
Every Wagon that extends `AbstractWagon` (SCP, HTTP, FTP and others) accepts a
flat
@@ -389,6 +411,8 @@ connection timeout in milliseconds, which applies to all
methods:
`connectionTimeout` inside `httpConfiguration` is the per-method alternative.
The `params`
`http.socket.timeout` and `http.connection.timeout` still take precedence over
both.
+<a id="HTTP_Headers"></a>
+
## Deprecated: `httpHeaders`
```xml
diff --git a/content/markdown/guides/mini/guide-wagon-providers.md
b/content/markdown/guides/mini/guide-wagon-providers.md
index bf63f4b4..a7d59b29 100644
--- a/content/markdown/guides/mini/guide-wagon-providers.md
+++ b/content/markdown/guides/mini/guide-wagon-providers.md
@@ -19,8 +19,13 @@ under the License.
# Guide to Selecting Alternative Wagon Providers
+<a id="Command-Line_Configuration"></a>
+<a id="settings.xml_Configuration"></a>
+
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.
+<a id="Available_Wagon_Providers"></a>
+
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).
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).