THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Code Block |
---|
svn co https://svn.apache.org/repos/asf/struts/struts2/trunk STRUTS_#_#_# |
Change site target
Edit the top pom.xml file and replace 2.x the url below with version number that's going to be released
Code Block | ||||
---|---|---|---|---|
| ||||
<distributionManagement>
<site>
<id>apache-site</id>
<url>scp://people.apache.org/www/struts.apache.org/2.x/</url>
</site>
</distributionManagement>
|
commit the change
Prepare release
Tag the release by using the "release:prepare" goal of Maven:
...
- Check out site src code
Code Block svn co https://svn.apache.org/repos/asf/struts/site/ struts-site
- Update xml files
- struts-site/src/site/xdoc/announce.xml (if applicable, refer also to corresponding security bulletin)
- struts-site/src/site/xdoc/downloads.xml (remove previous version)
- struts-site/src/site/xdoc/download.xml (remove previous version)
- struts-site/src/site/xdoc/index.xml
- struts-site/src/site/site.xml
- Commit the changes
- Generate the site
Code Block mvn site:site
- Open
struts-site/target/site/index.html
and verify the urls and versions are right - Deploy site
It takes a few hours for the site changes to go liveCode Block mvn site-deploy
Rollback site target
Revert back the site target to 2.x and commit the change
Permissions
After updating the site, be sure that the permissions are set to group writeable ($ chmod -R g+w .
)
...