-
Enhancement
-
Resolution: Done
-
Major
-
4.2.1.Final, 4.3.0.Alpha1
-
None
-
Sprint #1 April 2015, Sprint #2 April 2015
Since the JBT/JBDS Early Access site contains only JBT components, we should build it as an update site at the same time we're building the other JBT aggregates, rather than building it downstream from Central.
This would mean less target platform churning DURING a release, and speed up the way we do releases.
Later, if we end up with 3rd party stuff in EA, we can move to having TWO builds:
- one for JBT content (a subset of the JBT aggregate) and
- one for 3rd party content (an adjunct to the Central site)
This may mean moving some stuff like Sapphire into the JBDS TP, so that it's available should someone want to install Arquillian into JBDS. Or we could put it into Central, since it's a Central-EA dependency and need not be in JBDS itself.
- relates to
-
JBDS-3365 AngularJS support in JBT 4.2.3.Beta1 is newer than the version in JBDS 8.1.0.Beta1
- Closed
-
JBIDE-19473 Central can't load Discovery catalog
- Closed
-
JBIDE-19018 JBT Central Discovery staging site contains early access child site in its composite*.xml
- Closed
-
JBIDE-19038 Arquillian should not be in JBT EA catalog
- Closed
-
JBIDE-19025 Separate JBT and JBDS Central and EA sites
- Closed