]
Max Rydahl Andersen commented on JBIDE-18239:
---------------------------------------------
I simply do not understand why you think I'm saying *all* stuff in JBT should be in
JBDS. I'm saying the stuff that is in central TP now that comes from JBT builds just
as well could be added into the main jbds updatesite - that means things like Birt is
*not* going to end up in here.
And it has all to do with semantics of updatesites because this issue does not make any
sense without relying on the fact that JBDS-3086 is done that makes it so the / (root)
site is now a composite containing both main jbds content, extra from central etc.
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" ...?