This is an automated email from the ASF dual-hosted git repository.
mbuenger 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 fbe80caf Add link to resolver 1.x (#1484)
fbe80caf is described below
commit fbe80caf9aee2bca488fc7bfd17b61cee6ed9fc6
Author: Slawomir Jaranowski <[email protected]>
AuthorDate: Fri Dec 12 16:59:29 2025 +0100
Add link to resolver 1.x (#1484)
---
content/markdown/guides/mini/guide-resolver-transport.md | 8 ++++----
content/resources/components.links | 1 +
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/content/markdown/guides/mini/guide-resolver-transport.md
b/content/markdown/guides/mini/guide-resolver-transport.md
index a2274624..2abadec7 100644
--- a/content/markdown/guides/mini/guide-resolver-transport.md
+++ b/content/markdown/guides/mini/guide-resolver-transport.md
@@ -27,12 +27,12 @@ Plexus XML, which is not type safe, nor validated, nor
future-proof.
**Starting with Maven 3.9.0 release, the _default transport_ (the default
transport used by Maven Resolver)
changed from ancient Wagon to modern `maven-resolver-transport-http` aka
_native HTTP_ transport.**
-Take a peek at the Resolver [architecture
diagram](https://maven.apache.org/resolver-archives/resolver-LATEST-1.x/) and
the _transport_ box
+Take a peek at the Resolver [architecture
diagram](https://maven.apache.org/resolver-1.x/) and the _transport_ box
contains several implementations, and this number will probably increase.
The Resolver contains configuration for many aspects, including transport (see
the keys
prefixed with `aether.connector.`). They can be found on
-[resolver configuration
page](https://maven.apache.org/resolver-archives/resolver-LATEST-1.x/configuration.html).
+[resolver configuration
page](https://maven.apache.org/resolver-1.x/configuration.html).
**This page applies only to Maven 3.9.0 and newer.**
@@ -103,7 +103,7 @@ for example to allow the user to tell Maven how long to
wait before giving up on
## Low-level Resolver configuration
-All configuration items mentioned in [Configuration
Options](https://maven.apache.org/resolver-archives/resolver-LATEST-1.x/configuration.html)
+All configuration items mentioned in [Configuration
Options](https://maven.apache.org/resolver-1.x/configuration.html)
which are not mapped by `server/configuration` (eg.httpHeaders, timeout) tag
must be provided in special way.
Some resolver configuration properties has a flag `Supports Repo ID Suffix`.
@@ -186,7 +186,7 @@ to stick with Wagon, but migration to new transport is
warmly recommended.
Depending on which transport you use (`native`, `wagon` or something else),
you will want to refer to the corresponding
page(s) for detailed configuration options:
-* For Native HTTP transport detailed configuration user properties are
[collected on this
page](https://maven.apache.org/resolver-archives/resolver-LATEST-1.x/configuration.html).
+* For Native HTTP transport detailed configuration user properties are
[collected on this
page](https://maven.apache.org/resolver-1.x/configuration.html).
* For Wagon you want to use `-Dmaven.resolver.transport=wagon` user property
and [configuration from this
page](https://maven.apache.org/guides/mini/guide-http-settings.html).
* For any third party transport, please refer to its own documentation.
diff --git a/content/resources/components.links
b/content/resources/components.links
index 704cc619..cddb32da 100644
--- a/content/resources/components.links
+++ b/content/resources/components.links
@@ -33,6 +33,7 @@ resolver-ant-tasks=components/resolver-ant-tasks
resolver-archives=components/resolver-archives
resolver-demos=components/resolver-demos
resolver=components/resolver
+resolver-1.x=components/resolver-1.x
sandbox=components/sandbox
scm-archives=components/scm-archives
scm=components/scm
