Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5306

Should the :migrate operation remove the legacy extension in standalone?

    Details

    • Type: Enhancement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 10.0.0.Beta2
    • Fix Version/s: 10.0.0.CR1
    • Component/s: Management
    • Labels:
      None

      Description

      The :migrate management operation creates a new subsystem and removes the legacy subsystem. It also adds an extension for the new subsystem, but it doesn't remove the legacy extension.

      The legacy extension must of course stay in place in managed domain (the :migrate operation could be clever and check other profiles if they still have the subsystem, but I'd consider this behavior out of scope), but for standalone, I think the extension could and should be removed. Ideas?

      Brian noted [1] that there might be technical obstacles in removing the extension, in which case I of course agree with rejecting.

      [1] http://lists.jboss.org/pipermail/wildfly-dev/2015-August/004287.html

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  swd847 Stuart Douglas
                  Reporter:
                  lthon Ladislav Thon
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: