1717Contributing to [ Apache Maven Deploy Plugin] ( https://maven.apache.org/plugins/maven-deploy-plugin/ )
1818======================
1919
20- [ ![ ASF Jira] ( https://img.shields.io/endpoint?url=https%3A%2F%2Fmaven.apache.org%2Fbadges%2Fasf_jira-MDEPLOY.json )] [ jira ]
2120[ ![ Apache License, Version 2.0, January 2004] ( https://img.shields.io/github/license/apache/maven.svg?label=License )] [ license ]
21+ [ ![ Maven Central] ( https://img.shields.io/maven-central/v/org.apache.maven.plugins/maven-deploy-plugin.svg?label=Maven%20Central&versionPrefix=3. )] ( https://search.maven.org/artifact/org.apache.maven.plugins/maven-deploy-plugin )
2222[ ![ Maven Central] ( https://img.shields.io/maven-central/v/org.apache.maven.plugins/maven-deploy-plugin.svg?label=Maven%20Central )] ( https://search.maven.org/artifact/org.apache.maven.plugins/maven-deploy-plugin )
2323[ ![ Reproducible Builds] ( https://img.shields.io/badge/Reproducible_Builds-ok-green?labelColor=blue )] ( https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/maven/plugins/maven-deploy-plugin/README.md )
2424[ ![ Jenkins Status] ( https://img.shields.io/jenkins/s/https/ci-maven.apache.org/job/Maven/job/maven-box/job/maven-deploy-plugin/job/master.svg? )] [ build ]
@@ -34,7 +34,6 @@ things.
3434Getting Started
3535---------------
3636
37- + Make sure you have a [ JIRA account] ( https://issues.apache.org/jira/ ) .
3837+ Make sure you have a [ GitHub account] ( https://github.com/signup/free ) .
3938+ If you're planning to implement a new feature, it makes sense to discuss your changes
4039 on the [ dev list] [ ml-list ]] first.
@@ -60,37 +59,21 @@ There are some guidelines which will make applying PRs easier for us:
6059 + Create minimal diffs - disable on save actions like reformat source code or organize imports.
6160 If you feel the source code should be reformatted, create a separate PR for this change.
6261 + Check for unnecessary whitespace with ` git diff --check ` before committing.
63- + Make sure your commit messages are in the proper format. Your commit message should contain the key of the JIRA issue.
64- ```
65- [MDEPLOY-XXX] - Subject of the JIRA Ticket
66- Optional supplemental description.
67- ```
6862+ Make sure you have added the necessary tests (JUnit/IT) for your changes.
6963+ Run all the tests with ` mvn -Prun-its verify ` to assure nothing else was accidentally broken.
7064+ Submit a pull request to the repository in the Apache organization.
71- + Update your JIRA ticket and include a link to the pull request in the ticket.
7265
7366If you plan to contribute on a regular basis, please consider filing a [ contributor license agreement] [ cla ] .
7467
75- Making Trivial Changes
76- ----------------------
77-
78- For changes of a trivial nature to comments and documentation, it is not always
79- necessary to create a new ticket in JIRA. In this case, it is appropriate to
80- start the first line of a commit with '(doc)' instead of a ticket number.
81-
8268Additional Resources
8369--------------------
8470
8571+ [ Contributing patches] ( https://maven.apache.org/guides/development/guide-maven-development.html#Creating_and_submitting_a_patch )
86- + [ Apache Maven Deploy JIRA project page] [ jira ]
8772+ [ Contributor License Agreement] [ cla ]
8873+ [ General GitHub documentation] ( https://help.github.com/ )
8974+ [ GitHub pull request documentation] ( https://help.github.com/send-pull-requests/ )
9075+ [ Apache Maven Twitter Account] ( https://twitter.com/ASFMavenProject )
91- + #Maven IRC channel on freenode.org
9276
93- [ jira ] : https://issues.apache.org/jira/projects/MDEPLOY/
9477[ license ] : https://www.apache.org/licenses/LICENSE-2.0
9578[ ml-list ] : https://maven.apache.org/mailing-lists.html
9679[ code-style ] : https://maven.apache.org/developers/conventions/code.html
0 commit comments