You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by rf...@apache.org on 2013/06/30 23:48:39 UTC
svn commit: r1498188 - /maven/enforcer/trunk/README.TXT
Author: rfscholte
Date: Sun Jun 30 21:48:39 2013
New Revision: 1498188
URL: http://svn.apache.org/r1498188
Log:
Fix copy/paste URLs
Modified:
maven/enforcer/trunk/README.TXT
Modified: maven/enforcer/trunk/README.TXT
URL: http://svn.apache.org/viewvc/maven/enforcer/trunk/README.TXT?rev=1498188&r1=1498187&r2=1498188&view=diff
==============================================================================
--- maven/enforcer/trunk/README.TXT (original)
+++ maven/enforcer/trunk/README.TXT Sun Jun 30 21:48:39 2013
@@ -4,7 +4,7 @@ You can use the deploySite(.sh|.bat) scr
Without any profile, the site will be deployed to http://maven.apache.org/enforcer-archives/enforcer-${project.version}
sh ./deploySite.sh -Preporting
-To deploy main version http://maven.apache.org/maven-release, use
+To deploy main version http://maven.apache.org/enforcer, use
sh ./deploySite.sh -Preporting -Psite-release
Note you can add arguments to the script to pass your svn credentials:
@@ -16,7 +16,7 @@ Workflow for site when releasing
Once release staged, you can publish a staged site.
cd target/checkout
sh ./deploySite.sh -Preporting
-content will be in http://maven.apache.org/maven-release-archives/maven-release-${project.version}
+content will be in http://maven.apache.org/enforcer-archives/enforcer-${project.version}
Once vote passed, redeploy main site:
cd target/checkout (or use the version tag)