Google Git
Sign in
apache / maven-wrapper / refs/heads/origin-feature-jdk-enhancement
commitcb49488c19401a00f4c7440d7553f5c39e4fa2da[log] [tgz]
authorGuillaume Nodet <gnodet@gmail.com>Fri Jul 18 11:51:14 2025 +0200
committerGuillaume Nodet <gnodet@gmail.com>Fri Jul 18 11:51:14 2025 +0200
treeab4048dd0fed462bdbe52c3174813cfcc1698206
parent0f72fdb6aadc05acd94e71c3a274ea67e04befd2 [diff]
Add busybox wget support as fallback in only-mvnw script

- Enhanced only-mvnw script to try busybox wget when neither wget nor curl is available
- Added busybox wget detection in all HTTP request functions:
  * resolve_jdk_url() for JDK URL resolution API calls
  * redirect URL resolution logic
  * get_latest_version_from_disco() for version API calls
  * install_jdk() for JDK file downloads
  * main Maven distribution download section
- Updated error messages to include busybox wget as supported option
- Updated integration tests to handle busybox wget error messages
- Improves compatibility with minimal Linux environments like Alpine containers
3 files changed
tree: ab4048dd0fed462bdbe52c3174813cfcc1698206
  1. .github/
  2. maven-wrapper/
  3. maven-wrapper-distribution/
  4. maven-wrapper-plugin/
  5. src/
  6. .asf.yaml
  7. .gitignore
  8. Jenkinsfile
  9. NOTICE
  10. pom.xml
  11. README.md
README.md

Contributing to Apache Maven Wrapper

Apache License, Version 2.0, January 2004 Maven Central Reproducible Builds 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