[
https://issues.jboss.org/browse/JBIDE-19018?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-19018:
---------------------------------------------
yes I agree the confusion is co-locating things in staging that are not co-located at
release time.
But it is not only a problem if someone browses the updatesite - it hides or rather makes
things work that should not work. like if we had a bug in discoery site and marked
something without earlyaccess flag this would now be able to install ....if ea site was
not included this would fail and QE would more likely notice that something is wrong.
We did this split to ensure things would fail if we did mess things up ;)
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
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)