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

Thursday, 8 October 2015

    [
https://issues.jboss.org/browse/JBDS-3525?page=com.atlassian.jira.plugin....
] 

Nick Boldt commented on JBDS-3525:
----------------------------------

Curiously, once I've checked Arquillian in Central to be installed, the EA site
appears in the list of available software sites. So even if I then don't complete the
installation, I can Help > Check for updates and JBDS will find the 1.2.0.Final version
of Arquillian and can install it for me. 

So again, this seems like a bug. Should we:

a) add the EA content into the same URL as
https://devstudio.redhat.com/9.0/stable/updates/ so it's already available OOTB? No,
because then a user might Help > Install New Software and install something from the EA
site w/o realizing it's EA. They could have EA disabled and still do the install this
way.

b) add the EA URL by default into the list of Available Update Sites so it's available
& enabled OOTB? Maybe - at least that way it's clear that Arquillian and other EA
content comes from the EA site, not the main *supported* one.

c) figure out a way for the Help > Check for updates to hit the same URL(s) that back
JBT/JBDS Central, JBT/JBDS EA, and also the IS URLs too? Yeah, but the only thing I can
think of here to achieve this is (a) and (b). Can't see how Check for updates can ping
*hidden* URLs that are obfuscated behind Central w/o them simply being listed in the
Available Software Sites listing.

Thoughts?

...
 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: arquillian
    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
             Fix For: 9.0.1.GA, 10.0.0.Alpha1

 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)

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006