This is an automated email from the ASF dual-hosted git repository.
sjaranowski pushed a commit to branch maven-deploy-plugin-3.x
in repository https://gitbox.apache.org/repos/asf/maven-deploy-plugin.git
The following commit(s) were added to refs/heads/maven-deploy-plugin-3.x by
this push:
new 6dd30b3 Enable GitHub Issues
6dd30b3 is described below
commit 6dd30b3a63ffd542a2245cfc70b79a5156911465
Author: Slawomir Jaranowski <s.jaranow...@gmail.com>
AuthorDate: Sat Feb 22 18:27:29 2025 +0100
Enable GitHub Issues
---
README.md | 19 +------------------
pom.xml | 4 ++--
2 files changed, 3 insertions(+), 20 deletions(-)
diff --git a/README.md b/README.md
index 52b7b0f..77abb0f 100644
--- a/README.md
+++ b/README.md
@@ -17,8 +17,8 @@
Contributing to [Apache Maven Deploy
Plugin](https://maven.apache.org/plugins/maven-deploy-plugin/)
======================
-[][jira]
[][license]
+[](https://search.maven.org/artifact/org.apache.maven.plugins/maven-deploy-plugin)
[](https://search.maven.org/artifact/org.apache.maven.plugins/maven-deploy-plugin)
[](https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/maven/plugins/maven-deploy-plugin/README.md)
[][build]
@@ -34,7 +34,6 @@ things.
Getting Started
---------------
-+ Make sure you have a [JIRA account](https://issues.apache.org/jira/).
+ Make sure you have a [GitHub account](https://github.com/signup/free).
+ If you're planning to implement a new feature, it makes sense to discuss
your changes
on the [dev list][ml-list]] first.
@@ -60,37 +59,21 @@ There are some guidelines which will make applying PRs
easier for us:
+ 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 JIRA issue.
-```
-[MDEPLOY-XXX] - Subject of the JIRA Ticket
- Optional supplemental description.
-```
+ Make sure you have added the necessary tests (JUnit/IT) for your changes.
+ Run all the tests with `mvn -Prun-its verify` to assure nothing else was
accidentally broken.
+ Submit a pull request to the repository in the Apache organization.
-+ Update your JIRA ticket and include a link to the pull request in the ticket.
If you plan to contribute on a regular basis, please consider filing a
[contributor license agreement][cla].
-Making Trivial Changes
-----------------------
-
-For changes of a trivial nature to comments and documentation, it is not always
-necessary to create a new ticket in JIRA. In this case, it is appropriate to
-start the first line of a commit with '(doc)' instead of a ticket number.
-
Additional Resources
--------------------
+ [Contributing
patches](https://maven.apache.org/guides/development/guide-maven-development.html#Creating_and_submitting_a_patch)
-+ [Apache Maven Deploy JIRA project page][jira]
+ [Contributor License Agreement][cla]
+ [General GitHub documentation](https://help.github.com/)
+ [GitHub pull request
documentation](https://help.github.com/send-pull-requests/)
+ [Apache Maven Twitter Account](https://twitter.com/ASFMavenProject)
-+ #Maven IRC channel on freenode.org
-[jira]: https://issues.apache.org/jira/projects/MDEPLOY/
[license]: https://www.apache.org/licenses/LICENSE-2.0
[ml-list]: https://maven.apache.org/mailing-lists.html
[code-style]: https://maven.apache.org/developers/conventions/code.html
diff --git a/pom.xml b/pom.xml
index d05ed9e..cfefcb1 100644
--- a/pom.xml
+++ b/pom.xml
@@ -53,8 +53,8 @@ under the License.
<url>https://github.com/apache/maven-deploy-plugin/tree/${project.scm.tag}</url>
</scm>
<issueManagement>
- <system>JIRA</system>
- <url>https://issues.apache.org/jira/browse/MDEPLOY</url>
+ <system>GitHub</system>
+ <url>https://github.com/apache/maven-deploy-plugin/issues</url>
</issueManagement>
<ciManagement>
<system>Jenkins</system>
