Uploaded image for project: 'Red Hat CodeReady Studio (devstudio)'
  1. Red Hat CodeReady Studio (devstudio)
  2. JBDS-3525

Problems updating Early Access content between milestones (eg., Arquillian from Beta1 -> CR1, CR1 -> GA)

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Critical
    • 9.1.0.Beta1, 10.0.0.Alpha1
    • 9.0.0.Beta2
    • central
    • None
    • Hide

      1. Install JBDS 9.0.0.CR1 (from http://www.jboss.org/download-manager/file/jboss-devstudio-9.0.0.CR1-standalone_jar.jar as seen on http://www.jboss.org/products/devstudio/download/ )
      2. Install Arquillian 1.2.0.CR1 from https://devstudio.redhat.com/9.0/development/updates/discovery.earlyaccess/9.0.0.CR1/
      3. After install & restart of JBDS, go to Window > Preferences > Install/Update > Available Software Sites and delete or disable the above CR1 site. Leave only the https://devstudio.redhat.com/9.0/stable/updates/ site enabled.
      (this synthesizes having 9.0.0.CR1 and installing it from the older Central from CR1.)
      4. Enable EA in Central
      5. Make sure https://devstudio.redhat.com/9.0/stable/updates/earlyaccess/ is added and enabled in Window > Preferences > Install/Update > Available Software Sites
      6. Check for updates
      7. New Arquillian 1.2.0.Final is available, try to update it:

      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.Final-v20150925-0253-B27
No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.Final-v20150925-0253-B27
No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.Final-v20150925-0253-B27
No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.Final-v20150925-0253-B27
      Show
      1. Install JBDS 9.0.0.CR1 (from http://www.jboss.org/download-manager/file/jboss-devstudio-9.0.0.CR1-standalone_jar.jar as seen on http://www.jboss.org/products/devstudio/download/ ) 2. Install Arquillian 1.2.0.CR1 from https://devstudio.redhat.com/9.0/development/updates/discovery.earlyaccess/9.0.0.CR1/ 3. After install & restart of JBDS, go to Window > Preferences > Install/Update > Available Software Sites and delete or disable the above CR1 site. Leave only the https://devstudio.redhat.com/9.0/stable/updates/ site enabled. (this synthesizes having 9.0.0.CR1 and installing it from the older Central from CR1.) 4. Enable EA in Central 5. Make sure https://devstudio.redhat.com/9.0/stable/updates/earlyaccess/ is added and enabled in Window > Preferences > Install/Update > Available Software Sites 6. Check for updates 7. New Arquillian 1.2.0.Final is available, try to update it: 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.Final-v20150925-0253-B27 No repository found containing: osgi.bundle,org.jboss.tools.arquillian.maven.configurator,1.2.0.Final-v20150925-0253-B27 No repository found containing: osgi.bundle,org.jboss.tools.arquillian.ui,1.2.0.Final-v20150925-0253-B27 No repository found containing: org.eclipse.update.feature,org.jboss.tools.arquillian.feature,1.2.0.Final-v20150925-0253-B27
    • NEW

    Description

      JBDS notified me about a new update for Arquillian, but then after going into update it complains about:

      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

      Attachments

        Issue Links

          is related to

          Feature Request - Feature requests from customers and/or users JBIDE-20609 More accessible and visible Early Access content

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBDS-3537 Connection problems with https://devstudio.jboss.com/

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-18876 Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users JBIDE-20609 More accessible and visible Early Access content

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBDS-3538 read timeouts accessing JBDS discovery bits (possible Akamai problem?)

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              nickboldt Nick Boldt
              mnovotny@redhat.com Marek Novotny
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: