]
Nick Boldt commented on JBIDE-19025:
------------------------------------
Seems to me too that if we're splitting JBT [discovery + central update] and JBDS
[discovery + central update] we could migrate this content out of jbosstools-discovery and
into jbdevstudio-product + jbosstools-build-sites.
Separate JBT and JBDS Central and EA sites
------------------------------------------
Key: JBIDE-19025
URL:
https://issues.jboss.org/browse/JBIDE-19025
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: discovery
Reporter: Mickael Istria
Currently, we have to repeat (and update very often) some JBT artifacts in the Central
.target files because JBDS needs them.
This adds some long steps to the JBT staging process (
https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui...
), whereas this is a JBDS need.
So we should split the content of Central/EA update sites for JBT and JBDS, and have them
separated in distinct .target files: a Central/EA couple for JBT and another Central/EA
couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not
part of JBDS.
Since we're there, it would even be cleaner to have those artifacts in distinct repo,
so that JBDS wouldn't leak in JBT.