[jbosstools-issues] [JBoss JIRA] (JBDS-3525) Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA)

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBDS-3525:
--------------------------------------

I tried a variant of the steps to reproduce provided by [~akazakov] and managed to get Arquillian updated. However, instead of using "Check for updates", I did click "Show installed", selected "JBoss Arquillian" and clicked "Install/Update". Everything worked as expected, so it shows that the sites are not to blame.
Then I re-started from scratch and run exactly the steps to reproduce. And everything worked as expected too.
I'm enclined to believe that this is a symptom of the download problems we're facing. The download of p2 metadata may have failed and upgrade too as a consequence.

About the meaning of "Enable early-access", this should be treated in a separate Jira. Anyway, I feel it's interesting to explain the conceptual issues here:
Early-Access meaning has been evolving over its adoption. Currently, in UI, it only sets a preference allowing to "show early access content" in catalog. It was actually called like that initially, but "enable Early-Access" was preferred. The underlying early-access site used by early-access connectors is only added by p2 as an available site when installing some early-access content. So just ticking "enable early-access" doesn't make early-access content available when udpating.
It seems now that early-access isn't really a certificationId for a discovery entry nor a preference, but just a p2 repository with a specific URL; that enabling early-access is enabling this site as visible, and that an early-access connector is a connector that references this early-access site. However, it's not what's implemented in 4.3.0 and 9.0.0.
Actually, it's even possible that the definition proposed above is already outdated by the ability of other content providers (JBT-IS, JBDS-IS) to use an alternative site which is early-access. In such case, is the JBT-IS EA site expected to be visible when doing "Check for updates"...?

> Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA)
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-3525
>                 URL: https://issues.jboss.org/browse/JBDS-3525
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: central
>    Affects Versions: 9.0.0.Beta2
>         Environment: Version: 9.0.0.CR1
> Build id: CR1-v20150912-1100-B100
> Build date: 20150912-1100
> Enabled Early Access
>            Reporter: Marek Novotny
>            Assignee: Nick Boldt
>            Priority: Critical
>             Fix For: 9.0.1.GA, 10.0.0.Alpha1
>
>         Attachments: arquillian-in-jbt.png, updates-sites.xml
>
>
> JBDS notified me about a new update for Arquillian, but then after going into update it complains about:
> {noformat}
> An error occurred while collecting items to be installed
> session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
> No repository found containing: osgi.bundle,org.jboss.tools.arquillian.core,1.2.0.CR1-v20150911-0332-B19
> No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.CR1-v20150911-0332-B19
> No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.CR1-v20150911-0332-B19
> No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.CR1-v20150911-0332-B19
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)