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

Nick Boldt (JIRA) jira-events at lists.jboss.org
Wed Jul 24 14:38:26 EDT 2013


     [ https://issues.jboss.org/browse/JBDS-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt closed JBDS-2231.
----------------------------

         Assignee: Nick Boldt  (was: Douglas Palmer)
    Fix Version/s: 5.0.4.GA-SOA
                   5.0.3.GA-SOA
       Resolution: Done


Looks like this was already done ages ago, but of course no comments are to be found from [~charvolant] or [~doug.palmer]. :( Closing nonetheless.
                
> restructure JBDS staging update sites so that relative paths don't break when moved to production
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-2231
>                 URL: https://issues.jboss.org/browse/JBDS-2231
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: updatesite
>    Affects Versions: 5.0.0.GA
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 5.0.4.GA-SOA, 5.0.3.GA-SOA, 5.0.0.GA-SOA
>
>
> use either / paths in composite*.xml or move /5.0/staging/ to /5.0-staging/ so that paths will work locally for testing and on server once published

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list