You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by ma...@apache.org on 2021/01/13 19:59:07 UTC

[commons-daemon] branch master updated (110e8f0 -> f70b808)

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

markt pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/commons-daemon.git.


    from 110e8f0  Update copyright year to 2012
     new e45885f  Add previous version property to POM
     new f70b808  MOre automation for the release process

The 2 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:
 HOWTO-RELEASE.txt | 17 +++++++++++++----
 pom.xml           | 19 +++++++++++++++++++
 2 files changed, 32 insertions(+), 4 deletions(-)


[commons-daemon] 01/02: Add previous version property to POM

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

markt pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-daemon.git

commit e45885f98d54ffcb955c3473c40b803055d21de7
Author: Mark Thomas <ma...@apache.org>
AuthorDate: Wed Jan 13 11:26:24 2021 +0000

    Add previous version property to POM
---
 HOWTO-RELEASE.txt | 5 ++++-
 pom.xml           | 1 +
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/HOWTO-RELEASE.txt b/HOWTO-RELEASE.txt
index 4b77870..967c1a9 100644
--- a/HOWTO-RELEASE.txt
+++ b/HOWTO-RELEASE.txt
@@ -31,7 +31,10 @@ If you haven't already, add your public PGP key to KEYS.
 Update version numbers as needed
 --------------------------------
 
-Do a find for all the docs which include the previous version string
+Update the old version property (before tagging):
+ - /pom.xml                                     (commons.bc.version)
+
+Do a find for all the files which include the previous version string
 and replace it with the new version.
 
 These include:
diff --git a/pom.xml b/pom.xml
index 8c95279..251ea34 100644
--- a/pom.xml
+++ b/pom.xml
@@ -118,6 +118,7 @@
     <commons.release.version>1.2.4</commons.release.version>
     <commons.jira.id>DAEMON</commons.jira.id>
     <commons.jira.pid>12310468</commons.jira.pid>
+    <commons.bc.version>1.2.3</commons.bc.version>
   </properties>
 
   <build>


[commons-daemon] 02/02: MOre automation for the release process

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

markt pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-daemon.git

commit f70b8085f8f7c317a51138768e3cfe0dbdb245a0
Author: Mark Thomas <ma...@apache.org>
AuthorDate: Wed Jan 13 19:58:44 2021 +0000

    MOre automation for the release process
    
    After a lot of experimentation, I think I have found a way to get the
    Commons Daemon release process to work the way we need it to with the
    current iteration of the Commons Release plugin
---
 HOWTO-RELEASE.txt | 12 +++++++++---
 pom.xml           | 18 ++++++++++++++++++
 2 files changed, 27 insertions(+), 3 deletions(-)

diff --git a/HOWTO-RELEASE.txt b/HOWTO-RELEASE.txt
index 967c1a9..13e78fd 100644
--- a/HOWTO-RELEASE.txt
+++ b/HOWTO-RELEASE.txt
@@ -99,18 +99,24 @@ Maven tasks
 
 To deploy the Java jars to the Nexus staging repo:
 
-mvn deploy -Prelease [-Ptest-deploy]
+mvn deploy -Dcommons.release.isDistModule=true -Prelease [-Ptest-deploy]
 
 The test-deploy profile will deploy to target/deploy; omit for the live deploy
 
 Note: do not use clean in the same invocation.
-Remove the following artifacts and associated hashes/sigs before closing the
-repo:
+Remove the following artifacts and associated hashes/sigs from the Nexus staging
+repository before closing the repository:
 - tests.jar         (there are no tests, just a simple sample)
 - test-sources.jar  (there are no tests, just a simple sample)
 Do not remove the binary distributions since some users depend on Maven Central
 to obtain these.
 
+Note the Nexus repository ID (the number at the end of the repository name).
+
+Generate the release vote text with:
+
+mvn commons-release:vote-txt -Dcommons.nexus.repo.id=<repository-id>
+
 
 Updating the site
 -----------------
diff --git a/pom.xml b/pom.xml
index 251ea34..c9ae679 100644
--- a/pom.xml
+++ b/pom.xml
@@ -157,6 +157,24 @@
           <tarLongFileMode>gnu</tarLongFileMode>
         </configuration>
       </plugin>
+      <!-- Force detach-distributions to execute *after* Nexus deploy -->
+      <!-- we want these distributions deployed to both Nexus and dist.a.o -->
+      <plugin>
+        <artifactId>maven-deploy-plugin</artifactId>
+      </plugin>
+      <plugin>
+        <groupId>org.apache.commons</groupId>
+        <artifactId>commons-release-plugin</artifactId>
+        <executions>
+          <execution>
+            <id>detatch-distributions</id>
+            <phase>deploy</phase>
+            <goals>
+              <goal>detach-distributions</goal>
+            </goals>
+          </execution>
+        </executions>
+      </plugin>
     </plugins>
   </build>
   <profiles>