You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by sl...@apache.org on 2022/04/18 15:20:25 UTC

[maven-apache-parent] branch MPOM-286 updated (5e0d812 -> 67decf4)

This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a change to branch MPOM-286
in repository https://gitbox.apache.org/repos/asf/maven-apache-parent.git


    omit 5e0d812  [MPOM-286] org.apache:apache should conform with needed Sonatype checksums on deployment
     add 921022c  [MPOM-285] Upgrade Maven JAR Plugin to 3.2.2
     add ebf362c  Bump maven-compiler-plugin from 3.8.1 to 3.9.0
     add d66e12b  Revert "Bump maven-compiler-plugin from 3.8.1 to 3.9.0"
     add 5a878dc  [MPOM-288] - Update m-plugin-p to 3.6.4
     add dbca245  [MPOM-287] - Disable m2e warning for m-remote-resource-p:process
     add 60e0182  [MPOM-287] - Make m2e exclusion conditional by moving it to a profile only active in Eclipse
     add 6762787  Bump maven-release-plugin from 3.0.0-M4 to 3.0.0-M5
     add 9b8c9e3  Bump maven-scm-plugin from 1.12.0 to 1.12.2
     add 3a32b18  Use shared GitHub action v2
     add 83dcaac  add "Extensions" entry in left menu
     add 6ab189b  [MPOM-267] upgrade maven-javadoc-plugin to 3.3.2
     add 825f3ea  [MPOM-291] upgrade maven-compiler-plugin to 3.10.0
     add f77587d  [MPOM-291] upgrade maven-site-plugin to 3.11.0
     add a6fedf9  prepare ASF parent POM release 25
     add 55bc57d  [maven-release-plugin] prepare release apache-25
     add cc7dd4c  [maven-release-plugin] prepare for next development iteration
     add 4604141  prepare documentation for next iteration
     add 8c52ca6  [MPOM-310] switch to Matomo Maven site tracking (POM documentation)
     add 710b26e  Stage site build and use site-pom.xml
     add 708edb4  Bump maven-project-info-reports-plugin from 3.1.2 to 3.2.2
     add 170fdf5  Bump maven-dependency-plugin from 3.2.0 to 3.3.0
     add 16467a8  Bump maven-compiler-plugin from 3.10.0 to 3.10.1
     add 355daaf  Bump maven-shade-plugin from 3.2.4 to 3.3.0
     add 6633c71  [MPOM-305] Set minimum enforced Maven version to 3.2.5
     add 5537a1b  switch matomo.privacy.a.o to analytics.a.o
     add 95de444  Bump maven-clean-plugin from 3.1.0 to 3.2.0
     add 0952c0b  Fix jenkins url
     add 01834ce  prepare ASF parent POM release 26
     add 2c37c34  [maven-release-plugin] prepare release apache-26
     add b6df248  [maven-release-plugin] prepare for next development iteration
     add 855bccb  prepare documentation for next iteration
     new 67decf4  [MPOM-286] org.apache:apache should conform with needed Sonatype checksums 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   (5e0d812)
            \
             N -- N -- N   refs/heads/MPOM-286 (67decf4)

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:
 .github/workflows/maven-verify.yml |  6 +--
 pom.xml                            | 79 +++++++++++++++++++++++++++++++-------
 site-pom.xml                       |  4 +-
 src/site-docs/apt/index.apt.vm     |  6 ++-
 src/site-docs/site.xml             | 24 +++++++++++-
 5 files changed, 97 insertions(+), 22 deletions(-)


[maven-apache-parent] 01/01: [MPOM-286] org.apache:apache should conform with needed Sonatype checksums on deployment

Posted by sl...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a commit to branch MPOM-286
in repository https://gitbox.apache.org/repos/asf/maven-apache-parent.git

commit 67decf40547bcb1b19a8b72ffedff37d8a373ab0
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 checksums on deployment
---
 pom.xml | 56 ++++++++++++++++++++++++++++----------------------------
 1 file changed, 28 insertions(+), 28 deletions(-)

diff --git a/pom.xml b/pom.xml
index ecc0fda..04d4e36 100644
--- a/pom.xml
+++ b/pom.xml
@@ -375,6 +375,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>
 
@@ -447,34 +475,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>