]
Nick Boldt commented on JBIDE-19018:
------------------------------------
Yeah, I suppose we could do that, but we still need a Discovery site [0] w/ both plugins
in it [1], [2]. And it's only a problem if someone browses the update site [3] with p2
instead of with Central. Central shows the correct EA labelling. p2 does not (because
it's just an update site).
[0]
composite*.xml
I think part of the confusion here is that I chose to co-locate the Discovery site
(directory.xml + plugins) and the Update site (composite*.xml) at the same URL [4], for
convenience.
[4]
JBT Central Discovery staging site contains early access child site
in its composite*.xml
------------------------------------------------------------------------------------------
Key: JBIDE-19018
URL:
https://issues.jboss.org/browse/JBIDE-19018
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Reporter: Max Rydahl Andersen
Assignee: Nick Boldt
Priority: Critical
Fix For: 4.2.2.Final, 4.2.3.Final
http://download.jboss.org/jbosstools/discovery/staging/4.2.1.Final/ composites early
access site into the main update site, so anyone using that site as an update site (rather
than simply as the back end to Central) will see EA content as if it's from Central.
If we stop publishing this staging discovery site that includes EA content, the release
process will need to be updated to pull the EA plugin from another place.
Related to JBIDE-18984