Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-5707

Add a default impl of DeploymentUnitProcessor.undeploy; remove empty implementations

    XMLWordPrintable

Details

    Description

      Most DeploymentUnitProcessor implementations have no-op undeploy implementations. Save a bit of code/metaspace by adding a default no-op impl to the interface and then remove the per-implementation methods.

      Once this is done and integrated into full WildFly, a WFLY should be filed to clean up the DUPs there.

      Attachments

        Issue Links

          is related to

          Task - A task that needs to be done. WFLY-15722 Remove empty DeploymentUnitProcessor.undeploy implementations

          • 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

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: WFCORE

              People

                chaowan@redhat.com Chao Wang
                bstansbe@redhat.com Brian Stansberry
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: