[jira] Commented: (WW-1378) Need a Struts release or assembly build

["Ted Husted (JIRA)" <ji...@apache.org>]

    [ http://issues.apache.org/struts/browse/WW-1378?page=comments#action_37740 ] 
            
Ted Husted commented on WW-1378:
--------------------------------

So, with the documentation, here's the thing. One way or the other, we can export the Confluence space to HTML and integrate it with the website. There's a test export here.

* http://struts.apache.org/2.0/docs/Home.html

The formatting on the test run isn't great, but Pier's autoexport plug does a much better job. (I'd say a *stellar* job.) 

Right now, the infrastructure group is suggesting that all ASF projects check the formatted websites into Subversion, to simplify disaster recovery. (This is not consider the best idea, only a prudent idea for the time being.) One upside of doing a checkin is that the checkouts can be automated, so that we don't have to visit people.apache.org to update the website. We update SVN, and a cron job updates p.a.o. 

So, I wonder if we could use a website checkin as way to accomplish transfering HTML to SVN and exposing it to Maven. 

>From WW-1346:

1 Autoexport Plugin outputs Confluence space to HTML at location on Confluence server (twdata.org or cwiki.apache.org)
2 Cron job on Confluence server creates/refreshes zip archive of exported HTML in a downloadable location
3 Local build assembles/copies Maven output into a uniified website (/current/docs)
4 Local build downloads HTML zip archive from Confluence server and freshens local copy of exported s2 website (/current/docs/2.0/docs).

>From here we could scp the website as we do now, or go through SVN, as infrastructure suggests. 

5 Local build copies website files to current/docs
6 Committer checks in /current/docs folder to repository 
7 Committer or cron job updates website from repository

The big snag in exporting HTML to the website is access. We have to be careful about giving scripts write access to p.a.o. In this scenario, it's part of the build controlled by a committer. 

If we decide to try a website checkin, we could checkin the site now, including the test export of the s2 docs, and skip 4 until we have the plugin in place. (4 could even be done by a corn job on p.a.o.) 

-Ted. 



> Need a Struts release or assembly build
> ---------------------------------------
>
>                 Key: WW-1378
>                 URL: http://issues.apache.org/struts/browse/WW-1378
>             Project: Struts 2
>          Issue Type: New Feature
>            Reporter: Don Brown
>            Priority: Blocker
>             Fix For: 2.0.0
>
>
> We need a full release or assembly build to automate the process of creating a release as much as possible.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira