[
https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen commented on JBTIS-508:
-------------------------------------------
This url looks wrong:
http://download.jboss.org/jbosstools/discovery/stable/integration-stack/e...
I'm not sure at what point we started to ever merge the discovery site (the single jar
with a plugin.xml) with updatesites. It for sure never been a good idea - I always made it
very clear that discovery site != update site and I'll continue to do so and one of
the reasons is this situation. That the urls and streams so easily get mixed up.
It should at least be linked to a stream
i.e. main jbosstools site is at
http://download.jboss.org/jbosstools/earlyaccess/stable/luna/ and I would expect the
earlyaccess site from IS to just be composited into this existing site or if that is too
early to do (due to lack of automatiion or similar) I would have expected something like
http://download.jboss.org/jbosstools/earlyaccess/stable/luna/integration-... so it
matches the same pattern we have for the other sites.
wdyt?
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)