Google Git
Sign in
apache/maven-shared-incremental/refs/heads/master
commit
62601f1cd1f353117654e4c3ba155dc76206fe08
[log]
author
Sylwester Lachiewicz <slachiewicz@apache.org>
Mon Aug 10 01:40:05 2026 +0200
committer
Sylwester Lachiewicz <slachiewicz@apache.org>
Mon Aug 10 22:46:13 2026 +0200
tree
ef7724dce3d961007635839a37d04deca494e906
parent
8f5a89a10fed389dccf32d5ce8bd22cbaa8cee61 [diff]
Modernise the download page

This page was last touched in 2018 and still carried the ASF mirror-selection
form. The mirror network was retired in favour of a single CDN, so that form
now renders a "choose a mirror" dropdown offering exactly one entry,
dlcdn.apache.org. The checksum, signature and KEYS links still pointed at
www.apache.org/dist, which has been a 301 to downloads.apache.org for years.

The page now matches the form the rest of the Maven estate already uses,
finishing for this repository the sweep started in 2023:

  - the artifact from dlcdn.apache.org
  - the .sha512, .asc and KEYS from downloads.apache.org
  - older releases from archive.apache.org

Two things go with the mirror section, both worth a reviewer's attention:

  - its in-page anchors, #mirror and the version-numbered subsection anchor,
    which becomes the stable #Files. In-page only; no URL changes.
  - the paragraph linking to /guides/mini/guide-mirror-settings.html. That
    page is still live, but it is advice about configuring a repository
    mirror in settings.xml rather than about downloading a source release,
    and none of the ~43 repositories already on the current form carry it.
    Dropping it is what converges this page with the rest of the estate; say
    so on the PR if you would rather keep it here.

download.cgi is left in place. The ASF licence header is left exactly as it
was.

Generated-by: Claude Opus 5 (1M context)
1 file changed
tree: ef7724dce3d961007635839a37d04deca494e906
  1. .github/
  2. src/
  3. .asf.yaml
  4. .gitignore
  5. Jenkinsfile
  6. LICENSE
  7. pom.xml
  8. README.md
README.md

Contributing to Apache Maven Shared Incremental

Apache License, Version 2.0, January 2004 Maven Central Jenkins Status Jenkins tests

You have found a bug, or you have an idea for a cool new feature? Contributing code is a great way to give something back to the open source community. Before you dig right into the code, there are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.

Getting Started

  • Make sure you have a GitHub account.
  • If you‘re planning to implement a new feature, it makes sense to discuss your changes on the dev list first. This way you can make sure you’re not wasting your time on something that isn‘t considered to be in Apache Maven’s scope.
  • Submit a ticket for your issue, assuming one does not already exist.
    • Clearly describe the issue, including steps to reproduce when it is a bug.
    • Make sure you fill in the earliest version that you know has the issue.
  • Fork the repository on GitHub.

Making and Submitting Changes

We accept Pull Requests via GitHub. The developer mailing list is the main channel of communication for contributors.
There are some guidelines which will make applying PRs easier for us:

  • Create a topic branch from where you want to base your work (this is usually the master branch). Push your changes to a topic branch in your fork of the repository.
  • Make commits of logical units.
  • Respect the original code style: by using the same codestyle, patches should only highlight the actual difference, not being disturbed by any formatting issues:
    • Only use spaces for indentation.
    • Create minimal diffs - disable on save actions like reformat source code or organize imports. If you feel the source code should be reformatted, create a separate PR for this change.
    • Check for unnecessary whitespace with git diff --check before committing.
  • Make sure you have added the necessary tests (JUnit/IT) for your changes.
  • Run all the tests with mvn -Prun-its verify to assure nothing else was accidentally broken.
  • Submit a pull request to the repository in the Apache organization.

If you plan to contribute on a regular basis, please consider filing a contributor license agreement.

Additional Resources