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

Review SpringIDE 2.8.0 for inclusion in JBDS 5

    XMLWordPrintable

Details

    Description

      Current versions of SpringIDE included in JBDS are:

      JBDS 4.x :: SpringIDE 2.5
      JBDS 5.0 :: SpringIDE 2.7.2

      The purpose of this JIRA is to determine if we'd be better off using 2.8 instead of 2.7.

      Attachments

        Issue Links

          blocks

          Sub-task - The sub-task of the issue JBDS-1630 3rd party cert: springide 2.8

          • 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-1593 Detail what 3rd party projects should be included in JBDS 4.x

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

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1594 Detail what 3rd party projects should be included in JBDS 5.x

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

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1942 Beans Cross Reference view is not working

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

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1838 SpringIDE 2.6 breaks JBDS welcome page

          • 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-1943 Opening Dependency Graph in Spring Explorer through some bean is not working

          • 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
          is cloned by

          Task - Represents a small unit of work that is not end-user facing. JBDS-1863 Review SpringIDE 2.7.2 for inclusion in JBDS 5

          • 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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1910 Wrong version of Spring IDE installed

          • 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

          Sub-task - The sub-task of the issue JBDS-2280 Investigate use of SpringIDE 2.7.2 or 3 in JBoss 6 Central & JBDS Extras sites

          • 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

          Sub-task - The sub-task of the issue JBDS-2395 Investigate use of SpringIDE 3.2 in JBoss Central 7

          • 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. JBDS-2278 update JBT 4 / JBDS 6 Central to include latest 3rd party features

          • 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

          Task - Represents a small unit of work that is not end-user facing. JBDS-1868 Review Indigo SR1 for inclusion

          • 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

          Activity

            People

              ldimaggi@redhat.com Len DiMaggio
              nickboldt Nick Boldt
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: