[jbosstools-issues] [JBoss JIRA] (JBDS-3502) Instead of 4 zips, merge Central+TP and EA+TP into 2 composite repos for easier offline use (similar to what we had for JBDS 8)

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBDS-3502:
----------------------------------

Please compare the /snapshots page with the /development one. 

You'll see that there are only 2 Central zips listed: one for Central (includes Central TP) and one for EA (includes EA TP). 

Here's a screenshot showing TWO links: http://snag.gy/v2r5C.jpg
And here's the unchanged development page, with FOUR:  http://snag.gy/cBbCq.jpg

There's no duplication of content in these zips. 

* The Central one contains Central content from JBT + 3rd party content from the Central TP. 
* The EA one contains EA content from JBT + 3rd party content from the EA TP. 

Both are built here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-build-sites.aggregate.child-sites_master/
Results are here: 
* https://devstudio.redhat.com/9.0/snapshots/updates/central/master/
* https://devstudio.redhat.com/9.0/snapshots/updates/earlyaccess/master/

Then, these are referenced by Central's Discovery mechanism via these URLs:

https://devstudio.redhat.com/9.0/snapshots/updates/discovery.central/master/compositeArtifacts.xml
https://devstudio.redhat.com/9.0/snapshots/updates/discovery.earlyaccess/master/compositeArtifacts.xml

For CR1, we should change those composite sites so that they don't include BOTH a composite of Central+TP and a link to the same TP; so discovery.central becomes THREE child sites, not FOUR. 

---

{quote}Should it not just be main tools updatesite.zip (which is our components + Central + TP) and then one zip download for Earlyaccess (which you probably view as EA+ additional TP) ?{quote}

Since this is a change to the way the Central & EA zips are produced, it does not include the idea of merging JBT + JBT TP into a single zip (it's still two zips) or JBDS + JBDS TP into a single zip (that too is still two zips: one for the JBDS update site, and one for the JBDS TP). Yes, we could consider merging the target platform into the update site zip for JBT and JBDS, but that's for another JIRA. I proposed this in the build.next "future topics" page, but didn't open a JIRA yet.

"Should we bundle the JBT TP inside the JBT update site zip (as a composite, two folders, like IS does) ?" -- http://ether-man.rhcloud.com/p/build.next (line 46)

{quote}Or do you really imply that we will duplicate the same TP into both Earlyaccess and Central ?{quote}
Nope, did not imply that. Central and EA have separate TPs. You can see those .target files here:

https://github.com/jbosstools/jbosstools-discovery/blob/master/jbtcentraltarget/multiple/jbtcentral-multiple.target
https://github.com/jbosstools/jbosstools-discovery/blob/master/jbtearlyaccesstarget/multiple/jbtearlyaccess-multiple.target

So... no duplication is necessary. Really. :D




> Instead of 4 zips, merge Central+TP and EA+TP into 2 composite repos for easier offline use (similar to what we had for JBDS 8)
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-3502
>                 URL: https://issues.jboss.org/browse/JBDS-3502
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: build, central, updatesite
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>            Priority: Blocker
>             Fix For: 9.0.0.CR1
>
>
> Today the offline solution [1], [2] for installing stuff from Central or Early Access requires a pair of zips: the 3rd party content (target platform), and the stuff from JBoss Tools.
> [1] http://www.jboss.org/products/devstudio/download/ (Central Zip doesn't include the JBT stuff, just the 3rd party / TP content)
> [2] https://devstudio.redhat.com/9.0/staging/updates/ (both zips shown)
> We should combine these into a single, larger zip, such that the offline solution requires only a single zip and there's no confusion about what a Central Zip is.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)