[
https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBTIS-508:
-------------------------------------------
[~nickboldt] no problems with telling users to use the correct site that will actually
receive updates (i.e.
https://devstudio.redhat.com/9.0/development/updates/integration-stack/) as opposed to the
version specific one.
I'm just saying that the version specific site does not go away, it is still here for
QE to test against.
JBDS IS/JBT IS has this extra challenge that they need the version separated site since
they are targeting JBDS 9.0 where as our development might contain JBDS 9.1 bits - thus we
are risking a rather gnarly overlap/mismatch of sites in the current model ;/
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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)