You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by ti...@apache.org on 2022/01/13 18:07:12 UTC
[maven-apache-parent] branch MPOM-286 updated (d36d9ba -> 85c5ec9)
This is an automated email from the ASF dual-hosted git repository.
tibordigana pushed a change to branch MPOM-286
in repository https://gitbox.apache.org/repos/asf/maven-apache-parent.git.
discard d36d9ba [MPOM-286] org.apache:apache should conform with needed Sonatype signatures on deployment
new 85c5ec9 [MPOM-286] org.apache:apache should conform with needed Sonatype signatures on deployment
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (d36d9ba)
\
N -- N -- N refs/heads/MPOM-286 (85c5ec9)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
pom.xml | 50 +++++++++++++++++++++++++-------------------------
1 file changed, 25 insertions(+), 25 deletions(-)
[maven-apache-parent] 01/01: [MPOM-286] org.apache:apache should conform with needed Sonatype signatures on deployment
Posted by ti...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
tibordigana pushed a commit to branch MPOM-286
in repository https://gitbox.apache.org/repos/asf/maven-apache-parent.git
commit 85c5ec9f1c544c3c6fca7e704a6a25824442bb3b
Author: Tibor Digaňa <ti...@apache.org>
AuthorDate: Thu Jan 13 18:40:11 2022 +0100
[MPOM-286] org.apache:apache should conform with needed Sonatype signatures on deployment
---
pom.xml | 56 ++++++++++++++++++++++++++++----------------------------
1 file changed, 28 insertions(+), 28 deletions(-)
diff --git a/pom.xml b/pom.xml
index 822d3bd..b7b09ad 100644
--- a/pom.xml
+++ b/pom.xml
@@ -364,6 +364,34 @@ under the License.
</execution>
</executions>
</plugin>
+ <!-- calculate checksums of source release for Apache dist area -->
+ <plugin>
+ <groupId>net.nicoulaj.maven.plugins</groupId>
+ <artifactId>checksum-maven-plugin</artifactId>
+ <version>1.11</version>
+ <executions>
+ <execution>
+ <id>source-release-checksum</id>
+ <goals>
+ <goal>artifacts</goal>
+ </goals>
+ <!-- execute prior to maven-gpg-plugin:sign due to https://github.com/nicoulaj/checksum-maven-plugin/issues/112 -->
+ <phase>post-integration-test</phase>
+ <configuration>
+ <algorithms>
+ <algorithm>SHA-512</algorithm>
+ </algorithms>
+ <!-- https://maven.apache.org/apache-resource-bundles/#source-release-assembly-descriptor -->
+ <includeClassifiers>source-release</includeClassifiers>
+ <excludeMainArtifact>true</excludeMainArtifact>
+ <csvSummary>false</csvSummary>
+ <!-- attach SHA-512 checksum as well to upload to Maven Staging Repo,
+ as this eases uploading from stage to dist and doesn't do harm in Maven Central -->
+ <attachChecksums>true</attachChecksums>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
</plugins>
</build>
@@ -436,34 +464,6 @@ under the License.
</execution>
</executions>
</plugin>
- <!-- calculate checksums of source release for Apache dist area -->
- <plugin>
- <groupId>net.nicoulaj.maven.plugins</groupId>
- <artifactId>checksum-maven-plugin</artifactId>
- <version>1.11</version>
- <executions>
- <execution>
- <id>source-release-checksum</id>
- <goals>
- <goal>artifacts</goal>
- </goals>
- <!-- execute prior to maven-gpg-plugin:sign due to https://github.com/nicoulaj/checksum-maven-plugin/issues/112 -->
- <phase>post-integration-test</phase>
- <configuration>
- <algorithms>
- <algorithm>SHA-512</algorithm>
- </algorithms>
- <!-- https://maven.apache.org/apache-resource-bundles/#source-release-assembly-descriptor -->
- <includeClassifiers>source-release</includeClassifiers>
- <excludeMainArtifact>true</excludeMainArtifact>
- <csvSummary>false</csvSummary>
- <!-- attach SHA-512 checksum as well to upload to Maven Staging Repo,
- as this eases uploading from stage to dist and doesn't do harm in Maven Central -->
- <attachChecksums>true</attachChecksums>
- </configuration>
- </execution>
- </executions>
- </plugin>
<!-- We want to sign the artifact, the POM, and all attached artifacts (except for SHA-512 checksum) -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>