Contributing to Dependency Management Plugin

Dependency Management Plugin is released under the Apache 2.0 license. If you would like to contribute something, or simply want to work with the code, this document should help you to get started.

Code of conduct

This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to spring-code-of-conduct@pivotal.io.

Include a Signed-off-by Trailer

All commits must include a Signed-off-by trailer at the end of each commit message to indicate that the contributor agrees to the Developer Certificate of Origin (DCO). For additional details, please refer to the "Hello DCO, Goodbye CLA: Simplifying Contributions to Spring" blog post.

Code conventions and housekeeping

None of these is essential for a pull request, but they will all help

• Make sure all new .groovy files to have a simple Javadoc class comment with at least an @author tag identifying you, and preferably at least a paragraph on what the class is for.
• Add the ASF license header comment to all new .groovy files (copy from existing files in the project)
• Add yourself as an @author to the .groovy files that you modify substantially (more than cosmetic changes).
• Add some Javadocs
• Add unit tests that covers and new or modified functionality
• Whenever possible, please rebase your branch against the current main (or other target branch in the main project).
• When writing a commit message please follow these conventions. Also, if you are fixing an existing issue please add Fixes gh-nnn at the end of the commit message (where nnn is the issue number).

Working with the code

Building from source

The code is built with Gradle:

$ ./gradlew build