[jbosstools-issues] [JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119952#comment-13119952 ] 

Nick Boldt commented on JBTIS-508:
----------------------------------

Yes, the links to which I refer are *composites*, with actual version numbers carefully hidden underneath. Like we do for JBT and JBDS. 

My point when saying "instead" is that the pattern of 

* https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/
* https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/earlyaccess/

more closely aligns with the pattern of 

* https://devstudio.redhat.com/9.0/development/updates/integration-stack/
* https://devstudio.redhat.com/9.0/development/updates/integration-stack/earlyaccess/

thus making release process easier.... rather than linking to something like https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/discovery/9.0.0.Beta1/earlyaccess/ which would then include many nearly-duplicate early access plugin jars (see problems with this reported in JBTIS-498), and have a version-specific path segment. 

As I've said before only staging sites ought to have a version-specific URL because that way QE can differentiate between CR1 and CR1a. For CI builds, we only need a latest build and for development & stable, we definitely only want the latest. 

Make sense? It's the same protocol we're using for JBT & JBDS, so I hope you're OK with this, Max. :D

> 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://download.jboss.org/jbosstools/discovery/stable/integration-stack/
> {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.2.3.Final/compositeContent.xml which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4.2.3.Final/compositeContent.xml (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)