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

audit version numbers of features/plugins in JBDS 5.0.0 vs. 4.1.3

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 5.0.1.GA
    • 5.0.0.GA
    • build, updatesite
    • None

    Description

      Should have done this a while ago, but incorrectly assumed component leads were taking ownership of their versioning as they are the SMEs for their content and API changes.

      Hibernate should definitely be incremented since it's at version 3.4.1 in JBDS 4.1.3, but only 3.4.0 in 5.0.0.


      org_hibernate_eclipse=3.4.0
org_hibernate_eclipse_console=3.4.0
org_hibernate_eclipse_feature=3.4.0
org_hibernate_eclipse_help=3.4.0
org_hibernate_eclipse_jdt_apt_ui=3.4.0
org_hibernate_eclipse_jdt_ui=3.4.0
org_hibernate_eclipse_libs=3.4.0
org_hibernate_eclipse_mapper=3.4.0

      Based on screenshots above, should these be upversioned?

      org_jboss_ide_eclipse_archives_core=3.2.1
org_jboss_ide_eclipse_archives_feature=3.2.1
org_jboss_ide_eclipse_archives_jdt_integration=3.2.1
org_jboss_ide_eclipse_archives_ui=3.2.1


      org_jboss_tools_jmx_core=1.2.0
org_jboss_tools_jmx_feature=1.2.0
org_jboss_tools_jmx_ui=1.2.0


      org_jboss_tools_portlet_core=1.2.0
org_jboss_tools_portlet_feature=1.2.0
org_jboss_tools_portlet_ui=1.2.0


      org_jboss_tools_ws_core=1.2.2
org_jboss_tools_ws_creation_core=1.2.2
org_jboss_tools_ws_creation_ui=1.2.2
org_jboss_tools_ws_feature=1.2.2
org_jboss_tools_ws_jaxrs_core=1.2.2
org_jboss_tools_ws_jaxrs_feature=1.2.2
org_jboss_tools_ws_jaxrs_ui=1.2.2
org_jboss_tools_ws_ui=1.2.2

      Attachments

        1. 412vs500-feature-plugin-versions0.png
          45 kB
          Nick Boldt
        2. 412vs500-feature-plugin-versions1.png
          90 kB
          Nick Boldt
        3. 412vs500-feature-plugin-versions2.png
          21 kB
          Nick Boldt
        4. 412vs500-feature-plugin-versions3.png
          31 kB
          Nick Boldt
        5. 412vs500-feature-plugin-versions4.png
          73 kB
          Nick Boldt
        6. 412vs500-feature-versions.png
          79 kB
          Nick Boldt
        7. JBDS2212-central-upversion-33x.patch
          12 kB
          Nick Boldt
        8. JBDS2212-common-upversion-33x.patch
          54 kB
          Nick Boldt
        9. JBDS2212-examples-upversion-33x.patch
          11 kB
          Nick Boldt
        10. JBDS2212-jbds5-update-to-jbds501.png
          35 kB
          Nick Boldt
        11. JBDS2212-jst-upversion-33x.patch
          28 kB
          Nick Boldt
        12. JBDS2212-maven-upversion-33x.patch
          43 kB
          Nick Boldt
        13. JBDS2212-openshift-upversion-33x.patch
          16 kB
          Nick Boldt
        14. JBDS2212-portlet-upversion-33x.patch
          9 kB
          Nick Boldt
        15. JBDS2212-ws-upversion-33x.patch
          18 kB
          Nick Boldt

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-12248 JBoss Tools (Indigo) Installation from Eclipse Marketplace fails for Eclipse Indigo 3.7.0 and 3.7.1

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

          Sub-task - The sub-task of the issue JBIDE-13392 openshift tools should be version 2.3.2, not 2.3.1 in 3.3.x branch

          • 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-3031 For JBDS 8.0.0.Beta2: 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

          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) JBDS-3035 deprecate then remove JBDS audit-versions ant script

          • 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-12190 enable API Tooling for JBoss Tools components

          • 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.
          • Open

          Activity

            People

              nickboldt Nick Boldt
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: