You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by rh...@apache.org on 2022/06/14 23:29:44 UTC
svn commit: r1901921 - /db/derby/code/trunk/maven2/README.txt
Author: rhillegas
Date: Tue Jun 14 23:29:44 2022
New Revision: 1901921
URL: http://svn.apache.org/viewvc?rev=1901921&view=rev
Log:
DERBY-7136: Update maven instructions with the workaround which allowed me to publish the maven artifacts for 10.16.1.1; commit derby-7136-15-aa-recordMavenWorkaround.diff.
Modified:
db/derby/code/trunk/maven2/README.txt
Modified: db/derby/code/trunk/maven2/README.txt
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/maven2/README.txt?rev=1901921&r1=1901920&r2=1901921&view=diff
==============================================================================
--- db/derby/code/trunk/maven2/README.txt (original)
+++ db/derby/code/trunk/maven2/README.txt Tue Jun 14 23:29:44 2022
@@ -103,6 +103,14 @@ Description of the required steps:
mvn -Dgpg.passphrase="my secret passphrase" deploy
+ During the staging of 10.16.1.1, this step kept failing midway
+ with "peer not authenticated" errors. The problem was overcome
+ by re-issuing the command with a resume directive (in this case,
+ resuming at the Korean localizations where the original command
+ had errored out):
+
+ mvn -Dgpg.passphrase="my secret passphrase" deploy -rf :derbyLocale_ko_KR
+
e) Close the staging repository in Nexus.
Once you have deployed the artifacts you should close the staging
repository to allow others to test the artifacts. Log into