[Springframework-rcp-dev] [Spring-JIRA] Commented: (RCP-309) Archive the website for each release

[Jan H. (JIRA) <no...@sp...>]

    [ http://jira.springframework.org/browse/RCP-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_32783 ] 

Jan Hoskens commented on RCP-309:
---------------------------------

I think it would be better to have the whole site generated at a specific versioned url. This way all documentation is archived for each RCP version and keeps being consistent. We could then forward 'http://spring-rich-c.sourceforge.net' to the latest release.

Latest release can add a link to the previously generated apidocs (or whatever is needed). A new release can generate its site and only when everything  is in order, the forwarding is to be changed to the new version.

So I'm adding the ${project.version} variable to the site deployment url.

> Archive the website for each release
> ------------------------------------
>
>                 Key: RCP-309
>                 URL: http://jira.springframework.org/browse/RCP-309
>             Project: Spring Framework Rich Client Project
>          Issue Type: Bug
>          Components: Build System
>    Affects Versions: 0.1.0
>            Reporter: Larry Streepy
>            Assignee: Geoffrey De Smet
>
> Original issue:
> 1. Look at the deployed RCP website on sourceforge at http://spring-rich-c.sourceforge.net, nevigate to any of the module, support for example.
> 2. On that page, navigate to the javadocs.
> 3. Note the title Spring richclient support 0.2.0-SNAPSHOT API  instead of Spring richclient support 0.1.0-SNAPSHOT API 
> New issue:
> Archive the website on every release and place a link in site.xml

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