]
Max Rydahl Andersen commented on JBIDE-18239:
---------------------------------------------
You still seem to think i've been suggesting moving away from TP to define what is in
the updatesites - i'm not.
A) I don't know why we would hide the content from central on the main updatesite -
got an example of something that would not make sense there ? (at least I don't think
that could be a general blanket rule leaving out things here just because they are list in
central and not installed by default installer)
B) What I don't grok here is why this sounds like JBT and JBDS main updatesite is to
be treated different from each other ?
C) And no, I don't see me saying or suggesting us moving away from TP's to define
what is in early access and move to a category.xml format instead which does not have the
validation benefits and strictness that TP's has (thats at least what I see in the
PR's) - I simply suggested remove the duplicated JBT content in central. Nothing else.
But could we park this for f2f now ? Is there anything here that is critical for GA ?
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" ...?