Google Git
Sign in
apache / maven-jar-plugin / refs/tags/maven-jar-plugin-4.0.0-beta-1
tagbc3d5ef66dd2786976a6edbb5b886592d44ddef5
taggerGuillaume Nodet <gnodet@gmail.com>Wed Jun 26 10:28:47 2024 +0200
object86939e9698c1c0d2f9a057976de3ff58f214cebe 
[maven-release-plugin] copy for tag maven-jar-plugin-4.0.0-beta-1
commit86939e9698c1c0d2f9a057976de3ff58f214cebe[log] [tgz]
authorGuillaume Nodet <gnodet@gmail.com>Wed Jun 26 10:28:44 2024 +0200
committerGuillaume Nodet <gnodet@gmail.com>Wed Jun 26 10:28:44 2024 +0200
tree4bc384ace0360df8f024bbfbf8172b817d91dea6
parentd130798e5267bf358a1621cd373e226fc27cd132 [diff]
[maven-release-plugin] prepare release maven-jar-plugin-4.0.0-beta-1
1 file changed
tree: 4bc384ace0360df8f024bbfbf8172b817d91dea6
  1. .github/
  2. src/
  3. .asf.yaml
  4. .gitignore
  5. Jenkinsfile
  6. LICENSE
  7. NOTICE
  8. pom.xml
  9. README.md
README.md

Contributing to Apache Maven JAR Plugin

ASF Jira 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 JIRA account.
  • 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 your commit messages are in the proper format. Your commit message should contain the key of the JIRA issue.
[MJAR-XXX] - Subject of the JIRA Ticket
 Optional supplemental description.
  • 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.
  • 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.

Making Trivial Changes

For changes of a trivial nature to comments and documentation, it is not always necessary to create a new ticket in JIRA. In this case, it is appropriate to start the first line of a commit with ‘(doc)’ instead of a ticket number.

Additional Resources