2013/2/4 Rene Gielen <[email protected]>: > How did the SvnPubSub generation finally work out, time-wise? We had a > small chat where it seemed to be a really process for you to undergo... > is this a one-timer, or do we have to expect this pain for each and > every release?
The site is migrated to CMS and SvnPubSub (with was really painful :/) but INFRA must finally switch to push it to struts.a.o - this was already requested with [1]. I've updated Struts2 site configuration in the pom.xml to deploy website into production tree [2] and thus can invoked with command below: mvn clean site site:stage-deploy scm-publish:publish-scm It can be invoked only when vote passed as thus will automatically deploy a new version to struts.a.o which isn't a good idea before result of the vote ;-) I'm also updating the Release Guideline step-by-step and preparing some small scripts to help with the whole process of uploading new website and docs from Confluence - hope this will reduce the pain :P [1] https://issues.apache.org/jira/browse/INFRA-5659 [2] https://svn.apache.org/repos/infra/websites/production/struts/content/ [3] http://maven.apache.org/plugins/maven-scm-publish-plugin/examples/multi-module-configuration.html Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
