You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by kh...@apache.org on 2018/08/07 20:59:23 UTC

[maven-enforcer] branch MENFORCER-312 updated (773167c -> c1af9da)

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

khmarbaise pushed a change to branch MENFORCER-312
in repository https://gitbox.apache.org/repos/asf/maven-enforcer.git.


 discard 773167c  [MENFORCER-312] - Upgrade maven-parent to 32.
     new c1af9da  [MENFORCER-312] - Upgrade maven-parent to 32.  o Make it run on Maven 3.0.X

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   (773167c)
            \
             N -- N -- N   refs/heads/MENFORCER-312 (c1af9da)

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:
 maven-enforcer-plugin/pom.xml | 3 +++
 1 file changed, 3 insertions(+)


[maven-enforcer] 01/01: [MENFORCER-312] - Upgrade maven-parent to 32. o Make it run on Maven 3.0.X

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

khmarbaise pushed a commit to branch MENFORCER-312
in repository https://gitbox.apache.org/repos/asf/maven-enforcer.git

commit c1af9dac66739856cdb7691b843afa9f7673c02c
Author: Karl Heinz Marbaise <kh...@apache.org>
AuthorDate: Tue Aug 7 22:04:30 2018 +0200

    [MENFORCER-312] - Upgrade maven-parent to 32.
     o Make it run on Maven 3.0.X
---
 maven-enforcer-plugin/pom.xml | 7 +++++++
 pom.xml                       | 3 +--
 2 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/maven-enforcer-plugin/pom.xml b/maven-enforcer-plugin/pom.xml
index 42581d0..6729d40 100644
--- a/maven-enforcer-plugin/pom.xml
+++ b/maven-enforcer-plugin/pom.xml
@@ -112,6 +112,9 @@
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-plugin-plugin</artifactId>
+        <configuration>
+          <skipErrorNoDescriptorsFound>true</skipErrorNoDescriptorsFound>
+        </configuration>
         <executions>
           <execution>
             <id>descriptor-help</id>
@@ -163,6 +166,10 @@
               <goals>
                 <goal>validate</goal>
               </goals>
+              <properties>
+                <!-- e.g. ensure that Java7 picks up TLSv1.2 when connecting with Central -->
+                <https.protocols>${https.protocols}</https.protocols>
+              </properties>
             </configuration>
             <executions>
               <execution>
diff --git a/pom.xml b/pom.xml
index c9c17fe..b8c514f 100644
--- a/pom.xml
+++ b/pom.xml
@@ -23,7 +23,7 @@
   <parent>
     <artifactId>maven-parent</artifactId>
     <groupId>org.apache.maven</groupId>
-    <version>31</version>
+    <version>32</version>
     <relativePath>../pom/maven/pom.xml</relativePath>
   </parent>
   <groupId>org.apache.maven.enforcer</groupId>
@@ -65,7 +65,6 @@
   <properties>
     <maven.version>3.0</maven.version>
     <maven.site.path>enforcer-archives/enforcer-LATEST</maven.site.path>
-	<surefire.version>2.21.0</surefire.version>
   </properties>
 
   <dependencyManagement>