[Git][java-team/maven-deploy-plugin][upstream] New upstream version 3.1.4
Emmanuel Bourg (@ebourg)
gitlab at salsa.debian.org
Mon Mar 3 17:44:02 GMT 2025
Emmanuel Bourg pushed to branch upstream at Debian Java Maintainers / maven-deploy-plugin
Commits:
3695a0bf by Emmanuel Bourg at 2025-03-03T18:40:11+01:00
New upstream version 3.1.4
- - - - -
6 changed files:
- + .github/workflows/pr-automation.yml
- .github/workflows/release-drafter.yml
- README.md
- pom.xml
- src/it/deploy-bom/verify.groovy
- src/site/site.xml
Changes:
=====================================
.github/workflows/pr-automation.yml
=====================================
@@ -0,0 +1,27 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied. See the License for the
+# specific language governing permissions and limitations
+# under the License.
+
+name: PR Automation
+on:
+ pull_request_target:
+ types:
+ - closed
+
+jobs:
+ pr-automation:
+ name: PR Automation
+ uses: apache/maven-gh-actions-shared/.github/workflows/pr-automation.yml at v4
=====================================
.github/workflows/release-drafter.yml
=====================================
@@ -19,7 +19,12 @@ name: Release Drafter
on:
push:
branches:
- - master
+ - maven-deploy-plugin-3.x
+ workflow_dispatch:
+
jobs:
update_release_draft:
uses: apache/maven-gh-actions-shared/.github/workflows/release-drafter.yml at v4
+ with:
+ config-name: 'release-drafter-3.x.yml'
+
=====================================
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
=====================================
pom.xml
=====================================
@@ -28,7 +28,7 @@ under the License.
</parent>
<artifactId>maven-deploy-plugin</artifactId>
- <version>3.1.3</version>
+ <version>3.1.4</version>
<packaging>maven-plugin</packaging>
<name>Apache Maven Deploy Plugin</name>
@@ -49,12 +49,12 @@ under the License.
<scm>
<connection>scm:git:https://gitbox.apache.org/repos/asf/maven-deploy-plugin.git</connection>
<developerConnection>scm:git:https://gitbox.apache.org/repos/asf/maven-deploy-plugin.git</developerConnection>
- <tag>maven-deploy-plugin-3.1.3</tag>
+ <tag>maven-deploy-plugin-3.1.4</tag>
<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>
@@ -69,9 +69,9 @@ under the License.
<properties>
<javaVersion>8</javaVersion>
- <mavenVersion>3.9.6</mavenVersion>
+ <mavenVersion>3.9.9</mavenVersion>
<!-- Maven bound -->
- <resolverVersion>1.9.18</resolverVersion>
+ <resolverVersion>1.9.22</resolverVersion>
<!-- Maven bound -->
<slf4jVersion>1.7.36</slf4jVersion>
@@ -88,7 +88,7 @@ under the License.
<mavenSurefirePluginVersion>${version.maven-surefire}</mavenSurefirePluginVersion>
<mavenWarPluginVersion>${version.maven-war-plugin}</mavenWarPluginVersion>
- <project.build.outputTimestamp>2024-08-15T19:46:32Z</project.build.outputTimestamp>
+ <project.build.outputTimestamp>2025-02-23T17:23:46Z</project.build.outputTimestamp>
</properties>
<dependencies>
=====================================
src/it/deploy-bom/verify.groovy
=====================================
@@ -18,7 +18,6 @@
*/
def expectedDeploys = [
- 'org/apache/maven/its/deploy/bom/test/1.0/test-1.0-build.pom',
'org/apache/maven/its/deploy/bom/test/1.0/test-1.0.pom',
'org/apache/maven/its/deploy/bom/test/maven-metadata.xml',
]
=====================================
src/site/site.xml
=====================================
@@ -48,7 +48,7 @@ under the License.
<body>
<menu name="Overview">
<item name="Introduction" href="index.html"/>
- <item name="Goals" href="plugin-info.html"/>
+ <item name="Plugin Documentation" href="plugin-info.html"/>
<item name="Usage" href="usage.html"/>
<item name="FAQ" href="faq.html"/>
<!-- According to https://issues.apache.org/jira/browse/MNGSITE-152 -->
View it on GitLab: https://salsa.debian.org/java-team/maven-deploy-plugin/-/commit/3695a0bf72f61503d94486b263f3226aef952de3
--
View it on GitLab: https://salsa.debian.org/java-team/maven-deploy-plugin/-/commit/3695a0bf72f61503d94486b263f3226aef952de3
You're receiving this email because of your account on salsa.debian.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-commits/attachments/20250303/0d62f9cf/attachment.htm>
More information about the pkg-java-commits
mailing list