-
Enhancement
-
Resolution: Done
-
Major
-
4.2.2.Final
-
None
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_guide/8.0/JBT42_Staging_For_QE.adoc#rebuild-target-platforms-for-central-and-early-access ), 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.
- blocks
-
JBIDE-19336 To avoid disparity of versions, Central should not include the same IUs as JBT/JBDS update sites
- Closed
- is related to
-
JBIDE-18984 Build Early Access site as an update site, not a TP
- Closed
- relates to
-
JBDS-3348 FeedHenry feature isn't available in any JBDS site [9.0]
- Closed
-
JBIDE-19473 Central can't load Discovery catalog
- Closed
-
JBIDE-19038 Arquillian should not be in JBT EA catalog
- Closed