[jbosstools-issues] [JBoss JIRA] (JBDS-2231) restructure JBDS staging update sites so that relative paths don't break when moved to production

[ https://issues.jboss.org/browse/JBDS-2231?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2231: ---------------------------------- Partially completed for 5.0.1, but I need to verify docs are now up to date and that Doug is aware of the new path convention. Doug, if you look in SVN (https://svn.jboss.org/repos/devstudio/trunk/devstudio.jboss.com/updates/) you'll see I moved most of the stuff in /updates/5.0/staging/ to /updates/5.0-staging/ but left the SOA stuff as-is until we could talk about who might be publishing the staging URL to customers, etc. and who might be broken by the change. Also realized thx to Burr that some people may be running post-5.0.0, pre-5.0.1 updates (eg., a 5.0.1.CR build) and therefore may be looking at the staging site instead of the release site... so I've put metadata in the old location to redirect people. https://devstudio.jboss.com/updates/5.0/staging/central/core/compositeCon... -> https://devstudio.jboss.com/updates/5.0-staging/central/core/compositeCon... https://devstudio.jboss.com/updates/5.0/staging/central/core/compositeArt... -> https://devstudio.jboss.com/updates/5.0-staging/central/core/compositeArt... https://devstudio.jboss.com/updates/5.0/staging/central/core/ -> https://devstudio.jboss.com/updates/5.0-staging/central/core/ And... we need to update docs in here to reflect this change: https://svn.jboss.org/repos/devstudio/trunk/documentation/Release_Guide/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira