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

Allign deployment phases with OSGi terminology

    XMLWordPrintable

Details

    • Task
    • Resolution: Won't Do
    • Major
    • None
    • None
    • OSGi
    • None

    Description

      In OSGi we have

      • INSTALLED
      • RESOLVED
      • ACTIVE
      • UNINSTALLED

      It'd be useful to talk about modules and osgi bundles in the same jagon - i.e

      If a deployment is INSTALLED it has valid metadata
      If a deployment is RESOLVED it has Module/ClassLoader associated
      If a deployment is ACTIVE it can perform its normal operation
      If a deployment is UNINSTALLED it can be removed from the system

      The task here is mainly to rename/revisit the deployment phases

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. AS7-4243 Required changes to deployment layer

          • 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

          Activity

            Public project attachment banner

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

              People

                Unassigned Unassigned
                tdiesler@redhat.com Thomas Diesler
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: