[jbosstools-issues] [JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBDS-3208:
----------------------------------

FYI, I've shortformed the URLs for JBDS update sites.

Instead of devstudio.redhat.com/9.0/stable/updates/ and devstudio.redhat.com/9.0/development/updates/ we can drop the additional "/updates/" segment and just composite from the parent folder. Thus:

* devstudio.redhat.com/9.0/development/
* devstudio.redhat.com/9.0/stable/

Should people ( [~maxandersen] [~burrsutter] [~mickael_istria] [~dgolovin] ) want to simplify further,  we could make devstudio.redhat.com/9.0/ a composite of devstudio.redhat.com/9.0/stable/ to drop another path segment.

Details: https://github.com/jbdevstudio/jbdevstudio-product/pull/297

If we don't mind having the pre-GA builds point to the empty /stable/ site during the development of the milestones, we could drop out all the cruft in the p2.inf file [1] and just simplify things further. But it means that users will have to manually need to add the /development/ site to their JBDS Alpha or Beta build to get updates before we GA.

[1] https://github.com/nickboldt/jbdevstudio-product/blob/JBDS-3208_fixUpdateSiteURLs_43x/features/com.jboss.devstudio.core.feature/p2.inf

FYI to [~pleacu] - when it's time to stage the JBDS IS stuff, look in /9.0/staging/ not /updates/9.0-staging/ for your stuff.


> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
>                 Key: JBDS-3208
>                 URL: https://issues.jboss.org/browse/JBDS-3208
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 9.0.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 9.0.0.Alpha2
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> Latest suggestion:
> * /\{mars,9.0}/
> **  /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
> ***    /*updates*/
> ****     /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
> *****     /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
> ***    /*builds*/
> ****    /<job-name>/
> *****     /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/
> ---
> Older idea:
> {code}
> <download.jboss.org,devstudio.redhat.com>
>       <earlyaccess,updates,discovery>/<mars,9.0>
>        /snapshots [replace nightly]
>        /staging [rename content for QE, moves to development when approved]
>        /development
>        /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
>       drop /integration (not used)
>     builds/<jobname>/<buildid>
>     builds/<jobname>/composite*.xml for last N builds
>     targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when  it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. 
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.luna/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-composite-install_4.2.luna/



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)