[jbosstools-issues] [JBoss JIRA] (JBIDE-18239) Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-18239:
------------------------------------

Max, I said there are two options here. ( a ) or ( b ).

a) include all the JBT stuff that's NOT in JBDS into the JBDS/JBDS TP/Central composite [1]

or

b) create a new update site to include the stuff that's currently in Central/EA which comes from JBoss Tools and which is currently NOT part of JBDS.

Clearly you want ( b ). You could have just said that.

Re: "/" - it was always a composite site; the only difference after JBDS-3086 is that now the same composite URL is used for both JBDS and JBDS Central. 

To clarify another point ... are you OK that my PR puts the JBT content for Central [2] AND Early Access [3] into the same update site, or do you feel they need to be two different update sites?

[2] https://github.com/jbosstools/jbosstools-build-sites/pull/160/files#diff-691a1283f5e39c75e344402d5dfc8efbR9
[3] https://github.com/jbosstools/jbosstools-build-sites/pull/160/files#diff-691a1283f5e39c75e344402d5dfc8efbR19



> Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-18239
>                 URL: https://issues.jboss.org/browse/JBIDE-18239
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build, central, discovery, updatesite
>    Affects Versions: 4.2.0.CR1
>            Reporter: Nick Boldt
>              Labels: f2f2014
>             Fix For: 4.3.0.Alpha1
>
>         Attachments: JBIDE18239-proposed.png
>
>
> In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.).
> We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG.
> These would be produced as new zips using the JBT aggregate builder:
> https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/
> Need to decide what to call this... "Extras" "JBT-not-in-JBDS" "Shared" ...?



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