...
It's a good idea to keep that working copy to be used with future releases. Right now copy content of struts-site/content
to struts-production
, then commit changes. Next step is to update exported wiki pages. With current approach the pages are kept in struts-production/release/2.X.x/docs
where X
is the current branch (ie. 2.3.x, 2.2.x and so on). Simply remove the whole content from under /docs
and update it with docs from assembly (you can download one from Maven repository or copy generated during release process which supposes to be in struts/assembly/target/cwiki
). And commit changes.
Redeploy the
...
docs (Optional)
Checkout source of the website and export Confluence pages
Code Block svn co https://svn.apache.org/repos/asf/struts/site/trunk struts-site cd struts-site mvn package
Now the whole Confluence space is exported to
target/cwiki/WW/docs/
Checkout copy of production website
Code Block svn co https://svn.apache.org/repos/infra/websites/production/struts/content/ struts-production
(you can checkout just a subtree, but it's better to checkout the whole repo especially when you want to update also the main web page)
Update production
Code Block cp -r struts-site/target/cwiki/WW/docs/* struts-production/development/2.x/docs/ cd struts-production svn commit "Updates production"
...