Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-23528

(7.4.z) Upgrade Jandex from 2.2.3.Final-redhat-00001 to 2.4.2.Final-redhat-00001

    XMLWordPrintable

Details

    • Component Upgrade
    • Resolution: Done
    • Major
    • 7.4.6.CR1, 7.4.6.GA
    • None
    • Build System
    • None

    Description

      Upgrade Jandex from 2.2.3.Final-redhat-00001 to 2.4.2.Final-redhat-00001

      Tag: https://github.com/wildfly/jandex/releases/tag/2.4.2.Final
      Hash: b03b83783f89c803da01be4cdf7d3343295b4577
      Diff: https://github.com/wildfly/jandex/compare/2.2.3.Final...2.4.2.Final

      Attachments

        Issue Links

          clones

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-5779 Upgrade jandex to 2.4.2.Final

          • 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 incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-23557 (7.4.z) Upgrade WildFly Core from 15.0.13.Final-redhat-00001 to 15.0.14.Final

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-23337 Unable to read jandex.idx for smallrye reactive messaging jars in XP4

          • 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.
          • Ready for QA

          Activity

            People

              istudens@redhat.com Ivo Studensky
              chaowan@redhat.com Chao Wang
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: