Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-19473

Central can't load Discovery catalog

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 4.3.0.Alpha2
    • 4.3.0.Alpha2
    • central-update
    • None

    Description

      Both locally and with install-grinder, after installing nighly build from master, Central compains about "no connectors" found.

      The URL of the catalog seems right ( http://download.jboss.org/jbosstools/discovery/nightly/core/master/jbosstools-directory.xml ), referenced plugins are existing and seem to have right content.

      Log says

      !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-03-19 10:22:00.223
      !MESSAGE Unknown category 'org.jboss.tools.central.discovery.a.web' referenced by connector 'angularjs-eclipse-feature' declared in org.jboss.tools.central.discovery.earlyaccess_4.3.0.Alpha2_v20150318_0819_B3421.jar_8982963591780016496.jar

      I looked at jbosstoold-discovery history to see whether there was a suspicious change since last success (March 13th for install-grinder) and couldn't see anything related.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-19018 JBT Central Discovery staging site contains early access child site in its composite*.xml

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-19336 To avoid disparity of versions, Central should not include the same IUs as JBT/JBDS update sites

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-18984 Build Early Access site as an update site, not a TP

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-19025 Separate JBT and JBDS Central and EA sites

          • 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
          relates to

          Task - Represents a small unit of work that is not end-user facing. JBIDE-19608 For JBIDE 4.3.0.Alpha2: Code Freeze + Branch

          • 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

              mistria@redhat.com Mickael Istria
              mistria@redhat.com Mickael Istria
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: