From 5f539aba120c9639ff861eba9ab712e1813caad5 Mon Sep 17 00:00:00 2001 From: Sylwester Lachiewicz Date: Mon, 10 Aug 2026 01:28:42 +0200 Subject: [PATCH] Restore the common wording on the download page The wording here had drifted from the text the rest of the Maven estate uses. This restores the shared form so the page is identical to its counterparts apart from the distribution area and the artifact name. Comparing the rendered HTML before and after shows the reworded version had dropped three links, leaving the text as plain prose: the verification instructions, the KEYS file and the archive site. Restoring the common wording restores all three. The ASF licence header is left exactly as it was. Generated-by: Claude Opus 5 (1M context) --- src/site/xdoc/download.xml.vm | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/src/site/xdoc/download.xml.vm b/src/site/xdoc/download.xml.vm index 1e1e6a36..46b93e62 100644 --- a/src/site/xdoc/download.xml.vm +++ b/src/site/xdoc/download.xml.vm @@ -29,14 +29,14 @@ under the License.

${project.name} ${project.version} is distributed in source format.

-

Use a source archive if you want to build ${project.name} yourself.

+

Use a source archive if you intend to build ${project.name} yourself.

-

Otherwise, use the ready-made binary artifacts from the central repository.

+

Otherwise, simply use the ready-made binary artifacts from central repository.

${project.name} is distributed under the Apache License, version 2.0.

- +

This is the current stable version of ${project.name}.

@@ -58,16 +58,17 @@ under the License.
-

You must verify the integrity of the downloaded file using the checksum (.sha512 file) or using the signature (.asc file).

-

Use the public KEYS that Apache Maven developers provide to verify.

+

It is essential that you verify the integrity of the downloaded file + using the checksum (.sha512 file) + or using the signature (.asc file) against the public KEYS used by the Apache Maven developers. +

-

You must use the latest release version of ${project.name} to get new features and bug fixes.

-

Older releases exist on the archive site. These releases are not recommended.

+

It is strongly recommended to use the latest release version of ${project.name} to take advantage of the newest features and bug fixes.

+

Older non-recommended releases can be found on our archive site.

-