]
Nick Boldt commented on JBIDE-18239:
------------------------------------
To recap the proposal here
== NOW / CURRENT ==
Today we have one TP definition and therefore one update site for Central:
1. TP containing both 3rd party pieces that don't move often + JBT pieces that have to
be updated w/ every respin
== FUTURE / PROPOSED ==
In future we could have one TP definition AND an update site (category.xml) for Central:
1. TP containing both 3rd party pieces that don't move often
2. update site containing a subset of JBT pieces that have to be updated w/ every respin
(a new pom.xml+category.xml under
)
#NEEDINFO:
What shall we call this new update site? "Extras" "JBT-not-in-JBDS"
"Shared" ...?
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" ...?