Skip to content

docs: fix broken reference links #11692

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
amahi1568 wants to merge 1 commit into
base: master
Choose a base branch
from
+1 −1
Open

docs: fix broken reference links #11692

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ under the License.
<distributionId>apache-maven</distributionId>
<distributionShortName>Maven</distributionShortName>
<distributionName>Apache Maven</distributionName>
<maven.site.path>ref/4-LATEST</maven.site.path>
<maven.site.path>ref/4.0.0</maven.site.path>

@slawekjaranowski slawekjaranowski Feb 12, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

on master branch it is ok, we should change it on maven-4.0.x branch to something like ref/4.0-LATEST
@gnodet, @cstamas what do you think?

is is used to publish site candidate during release
https://maven.apache.org/components/ref/

maybe we should also add redirects to:
https://github.com/apache/maven-site/blob/master/content/filtered-resources/.htaccess

@gnodet, @cstamas what do you think?

@gnodet gnodet May 21, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change should not be made. 4-LATEST is the correct value — it's an intentional alias that always resolves to the latest 4.x release docs on the Maven site.

You can verify:

Additionally, master is currently on 4.1.0-SNAPSHOT, so hardcoding 4.0.0 would be doubly wrong.

<project.build.outputTimestamp>2025-06-24T20:18:00Z</project.build.outputTimestamp>
<!-- various versions -->
<asmVersion>9.9.1</asmVersion>
Expand Down
Loading