[commons-rng] 01/03: commons.release.dryRun flag is set in the test-deploy profile

[ah...@apache.org]

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

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

commit 9e9d7742a142b8f153d7b01188e3f94d997ab392
Author: aherbert <ah...@apache.org>
AuthorDate: Thu Sep 29 11:02:19 2022 +0100

    commons.release.dryRun flag is set in the test-deploy profile
    
    Explicit setting of this falg is not required.
---
 doc/release/release.howto.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/release/release.howto.txt b/doc/release/release.howto.txt
index 6a1acfbd..b4ac5c29 100644
--- a/doc/release/release.howto.txt
+++ b/doc/release/release.howto.txt
@@ -117,7 +117,7 @@ that the build process can create all the necessary artifacts.
   (1a)
   The command
 
-    $ JAVA_HOME="__Path_to_a_JDK__" mvn -Duser.name="__Your_Apache_id__" -Dcommons.release.dryRun=true -Ptest-deploy -Prelease clean verify site deploy
+    $ JAVA_HOME="__Path_to_a_JDK__" mvn -Duser.name="__Your_Apache_id__" -Ptest-deploy -Prelease clean verify site deploy
 
   should create the artifacts in the "target/deploy" directory. The site goal
   is required for the commons release plugin even though the site is