Menu
▾
▴
springframework-rcp-dev
|
From: Larry S. (JIRA) <no...@at...> - 2006-04-04 14:06:57
|
Generated module javadoc contains the wrong version number (0.2.0 instead of 0.1.0)
-----------------------------------------------------------------------------------
Key: RCP-309
URL: http://opensource.atlassian.com/projects/spring/browse/RCP-309
Project: Spring Framework Rich Client Project
Type: Bug
Components: Build System
Versions: 0.1.0
Reporter: Larry Streepy
Assigned to: Geoffrey De Smet
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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/spring/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Geoffrey De S. (JIRA) <no...@at...> - 2006-04-10 15:12:54
|
[ http://opensource.atlassian.com/projects/spring/browse/RCP-309?page=all ] Geoffrey De Smet updated RCP-309: --------------------------------- Summary: Archive the website for each release (was: Generated module javadoc contains the wrong version number (0.2.0 instead of 0.1.0)) Description: 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 was: 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 This is already been documented in releasechecklist, just have to deploy the site for 0.1.0 > Archive the website for each release > ------------------------------------ > > Key: RCP-309 > URL: http://opensource.atlassian.com/projects/spring/browse/RCP-309 > Project: Spring Framework Rich Client Project > Type: Bug > Components: Build System > 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://opensource.atlassian.com/projects/spring/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Peter De B. (JIRA) <no...@at...> - 2007-12-04 07:59:20
|
[ http://opensource.atlassian.com/projects/spring/browse/RCP-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_28225 ]
Peter De Bruycker commented on RCP-309:
---------------------------------------
the problem still exists: right now the docs have as title:
Spring richclient 0.3.0-SNAPSHOT API
http://spring-rich-c.sourceforge.net/apidocs/index.html
> Archive the website for each release
> ------------------------------------
>
> Key: RCP-309
> URL: http://opensource.atlassian.com/projects/spring/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://opensource.atlassian.com/projects/spring/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-04 08:37:12
|
[ 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
|
|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-11 15:18:10
|
[ http://jira.springframework.org/browse/RCP-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens closed RCP-309.
---------------------------
Assignee: Jan Hoskens (was: Geoffrey De Smet)
Resolution: Fixed
Fix Version/s: 1.0.0
Added version in website url:
http://spring-rich-c.svn.sourceforge.net/viewvc/spring-rich-c?view=rev&revision=1986
As this issue concerns the archiving and the added version doesn't override previous deployments, I consider this as fixed. At the moment of deployment we should point the site url to the new version.
> 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: Jan Hoskens
> Fix For: 1.0.0
>
>
> 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
|
Thanks for helping keep SourceForge clean.
X