Google Git
Sign in
apache / maven-shared-resources / refs/heads/master
commit48a07109ae408d662c19b061d3e48ac6920c3184[log] [tgz]
authorSlawomir Jaranowski <s.jaranowski@gmail.com>Mon Jan 13 21:51:26 2025 +0100
committerSlawomir Jaranowski <s.jaranowski@gmail.com>Wed Jan 15 22:05:17 2025 +0100
tree07cbf88d25ea555c35b5e7e139818abdf53da6af
parentdf109f4508bfb489cbe41ba85481d5172054f287 [diff]
Enable GitHub issues
7 files changed
tree: 07cbf88d25ea555c35b5e7e139818abdf53da6af
  1. .github/
  2. src/
  3. .asf.yaml
  4. .gitignore
  5. Jenkinsfile
  6. pom.xml
  7. README.md
README.md

Contributing to Apache Maven Shared Resources

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.
  • Submit a pull request to the repository in the Apache organization.
  • Update your JIRA ticket and include a link to the pull request in the ticket.

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

Additional Resources