[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=13060389#comment-13060389 ] 

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

Nowhere above did I say we were moving /builds *under* updatesite urls. I simply suggested that we could make /9.0/ a composite that points to /9.0/stable/updates/ to make the URL for the released bits simpler as it appears inside JBDS.

if you prefer the longer form of  /9.0/stable/updates/ then we can certainly do that.

Please link to related jira re: "improving this situation by letting ide.properties tell eclipse to suggest user to add a dev updatesite until GA is out." Do you mean JBDS-3191 ? In there Mickael said, "I suggest that the final site be ALWAYS added to the referenced site, even if it's empty."

If you want to remove all the p2.inf stuff that toggles between /development/ and /stable/, I can get that done ASAP and respin in time for the QE push tomorrow. But adding more ide-config.properties magic won't happen for Alpha2.

> 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)