]
Max Rydahl Andersen commented on JBTIS-508:
-------------------------------------------
Yes, that is what we discussed we would do for devstudio 8 when we refactored central to
be composited into the main updatesite.
I don't see a problem in having IS have an empty EA site linked in if that makes
publishing more uniform (no need to remove it if the content is just empty).
integration stack update sites mix discovery and earlyaccess causing
inconsistent update mechanism
--------------------------------------------------------------------------------------------------
Key: JBTIS-508
URL:
https://issues.jboss.org/browse/JBTIS-508
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: releng
Reporter: Max Rydahl Andersen
Assignee: Paul Leacu
Priority: Blocker
While reviewing JBIDE-20803 I noticed the following:
{code}
jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo...
{code}
The stable release for 4.2.4 is stated to point to the stable integration stack url which
on surface looks good:
But there are a few problems:
1) why not just point to
http://download.jboss.org/jbosstools/updates/stable/luna/ and
have the above internal detail url composited in ?
2) the actual composite behind it right now is
http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4...
which links in
http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4...
(our main sites should never composite earlyaccees since then when users install supported
versions they suddenly will now also have access to earlyaccess.
#1 is mainly just to reduce the number of updatesites actually necessary for users to
work with
#2 seems to be something inherent broken in the IS build since earlyaccess shold *never*
be aggregated into the release site.
Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site.
I would also have expected that the discovery site with the discovery plugins was kept
*separate* from the actual update sites to avoid any coupling between these.