[jbosstools-issues] [JBoss JIRA] (JBIDE-18594) Create a consistent /staging/ URL for JBT

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012078#comment-13012078 ] 

Nick Boldt commented on JBIDE-18594:
------------------------------------

Fix to composite*.xml files, applied in master and pushed to server: 

https://github.com/jbosstools/jbosstools-download.jboss.org/pull/424

> Create a consistent /staging/ URL for JBT
> -----------------------------------------
>
>                 Key: JBIDE-18594
>                 URL: https://issues.jboss.org/browse/JBIDE-18594
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>    Affects Versions: 4.2.0.CR2
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>            Priority: Critical
>              Labels: respin-a, respin-b
>             Fix For: 4.2.0.CR2
>
>
> Currently, the site we use for staging are organized much differently from what will be shipped to end-users. This results in making tests against staging behaving differently to how release will believe, so making tests confusing, error-prone and useless.
> We need to rework the staging process so that its output is similar to what will be the output of a release:
> * updates/staging/luna , compositing
> ** target-platform
> ** JBT core
> ** Central TP
> * earlyaccess site (location still to be decided?), currently 'http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.40.0.CR1-SNAPSHOT/REPO/
> Those sites are the one that need to be used respectively for jboss.discovery.site.ul and jboss.discovery.earlyaccess.site.url in ide-config.properties
> Then the process of releasing to development isn't much more than a _cp -r_ and some _sed /staging/development/_



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)