Spring Initializr is released under the Apache 2.0 license. If you would like to contribute something, or simply want to hack on the code this document should help you get started.
This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].
We use GitHub issues to track bugs and enhancements. If you have a general usage question please ask on Stack Overflow or join us on the Gitter channel.
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.
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.
Make sure all new .java
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 .java
files (copy from existing files
in the project)
Add yourself as an @author
to the .java files that you modify substantially (more
than cosmetic changes).
Add some Javadocs and, if you change the namespace, some XSD doc elements.
A few unit tests would help a lot as well — someone has to do it.
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-XXXX
at the end of the commit
message (where XXXX is the issue number).
Spring Initializer source can be build from the command line using
Apache Maven on JDK 1.8 or above.
We include ‘Maven Wrapper’ scripts (./mvnw
or mvnw.bat
) that you can run rather
than needing to install Maven locally.
The project can be built from the root directory using the standard Maven command:
$ ./mvnw clean install
The project also has Selenium tests that instrument the client side. In order to run them you need first to install Firefox and the latest geckodriver.
Once those are installed you can run the smoke tests by enabling an extra profile:
$ ./mvnw verify -PsmokeTests
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。