See the project site for more information.
A simple application that demonstrates the use of Spring CredHub is available in this repository.
Basic Compile and Test
To build the source you will need to install JDK 1.8.
Spring CredHub uses Gradle for most build-related activities, and you should be able to get off the ground quite quickly by cloning the project you are interested in and typing
$ ./gradlew install
Spring CredHub is released under the non-restrictive Apache 2.0 license, and follows a very standard Github development process, using Github tracker for issues and merging pull requests into master. If you want to contribute even something trivial please do not hesitate, but follow the guidelines below.
Sign the Contributor License Agreement
Before we accept a non-trivial patch or pull request we will need you to sign the Contributor License Agreement. Signing the contributor’s agreement does not grant anyone commit rights to the main repository, but it does mean that we can accept your contributions, and you will get an author credit if we do. Active contributors might be asked to join the core team, and given the ability to merge pull requests.
Code of Conduct
Code Conventions and Housekeeping
None of these is essential for a pull request, but they will all help. They can also be added after the original pull request but before a merge.
Use the Spring Framework code format conventions. If you use Eclipse you can import formatter settings using the
eclipse-code-formatter.xmlfile from the project. If using IntelliJ, you can use the Eclipse Code Formatter Plugin to import the same file.
Make sure all new
.javafiles to have a Javadoc class comment with at least an
@authortag identifying you, and preferably at least a paragraph on what the class is for.
Add the ASF license header comment to all new
.javafiles (copy from existing files in the project)
Add yourself as an
@authorto the .java files that you modify substantially (more than cosmetic changes).
Please include unit tests.
If no-one else is using your branch, please rebase it against the current master (or other target branch in the main project).
When writing a commit message please follow these conventions, if you are fixing an existing issue please add
Fixes gh-XXXXat the end of the commit message (where XXXX is the issue number).