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 2020/01/18 16:01:10 UTC

svn commit: r1872961 - /db/derby/code/trunk/maven2/README.txt

Author: rhillegas
Date: Sat Jan 18 16:01:09 2020
New Revision: 1872961

URL: http://svn.apache.org/viewvc?rev=1872961&view=rev
Log:
DERBY-7065: Update http to https in maven publication script; commit DERBY-7065.maven2.README.diff , contributed by Davide Grandi.

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=1872961&r1=1872960&r2=1872961&view=diff
==============================================================================
--- db/derby/code/trunk/maven2/README.txt (original)
+++ db/derby/code/trunk/maven2/README.txt Sat Jan 18 16:01:09 2020
@@ -117,10 +117,10 @@ Description of the required steps:
     Some time after you have released the artifacts from the temporary Apache
     staging repository in step (f), they should appear in the central Maven
     repository:
-        http://repo1.maven.org/maven2/org/apache/derby/
+        https://repo1.maven.org/maven2/org/apache/derby/
     After a few more days, the artifacts may also have propagated to other
     repositories / services, for instance the one below:
-        http://mvnrepository.com/artifact/org.apache.derby
+        https://mvnrepository.com/artifact/org.apache.derby
 
     Note that for the 10.6.1 release, within a day the artifacts turned up in
     the central Maven repository (the first link). It took 6 days for the