Bump org.apache.maven.plugins:maven-scm-plugin from 2.0.1 to 2.1.0

Bumps [org.apache.maven.plugins:maven-scm-plugin](https://github.com/apache/maven-scm) from 2.0.1 to 2.1.0.
- [Commits](https://github.com/apache/maven-scm/compare/maven-scm-2.0.1...maven-scm-2.1.0)

- dependency-name: org.apache.maven.plugins:maven-scm-plugin
  dependency-type: direct:production
  update-type: version-update:semver-minor

Signed-off-by: dependabot[bot] <support@github.com>
1 file changed
tree: 3a2d1737342df77cf596cbdff0131cf006ad6421
  1. .github/
  2. docs/
  3. .asf.yaml
  4. .gitignore
  5. Jenkinsfile
  6. pom.xml
  7. README.md

Contributing to Apache Software Foundation Parent POM

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

Have you found a bug or 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, please discuss your changes on the developer mailing 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 issue.
[#issue-numebr] - Subject of the issue
 Optional supplemental description.
  • Update the site documentation accordingly in docs/src/site and build it via mvn site -f docs
  • 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.

Making Trivial Changes

For changes of a trivial nature to comments and documentation, or other simple changes it is not always necessary to create a new issue.
In this case, it is appropriate to skip the issue from a commit message.

Additional Resources