Author: hboutemy
Date: Tue May 1 22:34:16 2012
New Revision: 1332871
URL: http://svn.apache.org/viewvc?rev=1332871&view=rev
Log:
added command with scm-publish plugin to update svn content with staged site
Modified:
maven/site/branches/INFRA-4466/trunk/content/apt/developers/release/maven-plugin-release.apt
Modified:
maven/site/branches/INFRA-4466/trunk/content/apt/developers/release/maven-plugin-release.apt
URL:
http://svn.apache.org/viewvc/maven/site/branches/INFRA-4466/trunk/content/apt/developers/release/maven-plugin-release.apt?rev=1332871&r1=1332870&r2=1332871&view=diff
==============================================================================
---
maven/site/branches/INFRA-4466/trunk/content/apt/developers/release/maven-plugin-release.apt
(original)
+++
maven/site/branches/INFRA-4466/trunk/content/apt/developers/release/maven-plugin-release.apt
Tue May 1 22:34:16 2012
@@ -45,7 +45,9 @@ Releasing A Maven Plugin
+------+
cd target/checkout
-mvn site-deploy -Preporting
+#mvn site-deploy -Preporting
+mvn -Preporting site site:stage scm-publish:publish-scm \
+
-Dscmpublish.pubScmUrl=https://svn.apache.org/repos/infra/websites/production/maventest/content/plugins/maven-XXX-plugin-latest
svn cp
https://svn.apache.org/repos/infra/websites/production/maventest/content/plugins/maven-XXX-plugin-latest
\
https://svn.apache.org/repos/infra/websites/production/maventest/content/plugins/maven-XXX-plugin-Y.Z
+------+
@@ -64,6 +66,7 @@ http://maven.apache.org/plugins/maven-XX
After the release has passed, the site needs to be updated to point to the
new release:
+-------+
+# just tested but could not make the following command work
svnmucc -U
https://svn.apache.org/repos/infra/websites/production/maventest/content/plugins
\
put =(printf "link maven-XXX-plugin-Y.Z") maven-XXX-plugin \
propset svn:special '*' maven-XXX-plugin
@@ -83,7 +86,7 @@ svnmucc -U https://svn.apache.org/repos/
* idea to be developped if sufficient people is interested
- Instead of doing command line svn and svnmucc operations and extpaths.txt
edits, the staging/release operations could be available
+ Instead of doing command line svn and svnmucc operations and extpaths.txt
edits, the staging/release operations could be automated
as web ui like following:
* http://cms.apache.org/maventest/release/plugins/maven-xxx-plugin-X.Y could
display a page proposing to <<stage the release
@@ -92,4 +95,4 @@ svnmucc -U https://svn.apache.org/repos/
* next time this page is displayed, with the content already available in
svn, the page could propose 2 different actions:
<<drop the staged documentation>> (with extpaths.txt removal) or <<publish
the release website>>.
- []
+ []
\ No newline at end of file
