Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-10221 Track component upgrades - EAP 5.3
  3. JBPAPP-10645

Upgrade JBoss VFS to 2.2.3.GA

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Done
    • Major
    • EAP_EWP 5.3.0.ER1
    • None
    • Build
    • None
    • Not Required
    • NEW

    Description

      Upgrade VFS to include the linked bug fixes

      Attachments

        Issue Links

          incorporates

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-10642 Jars not containing directory entries not properly reinitialized by VFS

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

          Bug - A problem that impairs or prevents the functions of the product. JBVFS-184 Jars not containing directory entries are not properly reinitialized

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

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-10082 AbstractVirtualFileHandler log message: "No such existing handler, falling back to old root + path" is too strict

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

          Bug - A problem that impairs or prevents the functions of the product. JBVFS-187 AbstractVirtualFileHandler log message: "No such existing handler, falling back to old root + path" is too strict

          • 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

          Activity

            People

              huwang@redhat.com Hui Wang
              rhn-engineering-cdewolf Carlo de Wolf
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: