[
https://issues.jboss.org/browse/JBIDE-18239?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-18239:
----------------------------------------
I have a few questions:
* Still, what's wrong with directly putting 0.0.0 for JBT stuff in target definition?
* In the end, why do we need at all to have JBT/JBDS parts in target definition if
it's not meant to get into the "extra" site?
* Mainly in case of JBDS, are we sure that all JBT/JBDS we have in the Central catalog
would be part of the main JBDS site? If not, then we still need to copy the necessary JBT
features to the extra site.
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)