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

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

Only problem w/ Max's new plan is that:

a) JBDS Central will need to point at JBT Aggregate site to resolve the missing JBT pieces, which is a no-no (can't install from .org into .com)
 - or -
b) JBDS Central will need to point at A COPY OF the JBT Aggregate site to resolve the missing JBT pieces, which sucks as it means we'll be putting JBT site on both .org and .com server. 

Max said above, "why have the content duplicated?" Because we have to according to the "don't cross the streams" rule.

Still, this is simpler. But it means that EVERYTHING in JBT will be theoretically browsable by a JBDS user if they look at the composite site (that contains JBT Central + JBT Aggregate) within their Eclipse/JBDS via Help > Install New.

Are we ok with exposing ALL of JBT from within JBDS? If not, then we *need* a new update site and can't just reuse the existing JBT aggregate within the JBDS Central composite.

[~maxandersen] [~mickael_istria] wdyt?

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