[
https://issues.jboss.org/browse/JBIDE-18984?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-18984:
-------------------------------
Description:
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 someon i
was:
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)
Build Early Access site as an update site, not a TP
----------------------------------------------------
Key: JBIDE-18984
URL:
https://issues.jboss.org/browse/JBIDE-18984
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, target-platform, updatesite
Affects Versions: 4.2.1.Final, 4.3.0.Alpha1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.3.0.Alpha1
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 someon i
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)