Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-686

Move content app framework to its own maven module

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Neutral Neutral
    • 5.0
    • None
    • None
    • Yes

      Name of the new module should be: magnolia-ui-content-app
      an have package info.magnolia.ui.contentapp

      It will have to depend on admincentral for now.

      We should move the following classes and packages there:

      • info.magnolia.ui.admincentral.app.content
      • info.magnolia.ui.admincentral.content.item
      • info.magnolia.ui.admincentral.content.action
      • info.magnolia.ui.admincentral.workbench
      • info.magnolia.ui.admincentral.form.action.CreateItemAction
      • info.magnolia.ui.admincentral.form.action.CreateItemActionDefinition
      • info.magnolia.ui.admincentral.dialog.ChooseDialogPresenter
      • info.magnolia.ui.admincentral.dialog.ChooseDialogPresenterFactory
      • info.magnolia.ui.admincentral.dialog.ChooseDialogView
      • info.magnolia.ui.admincentral.dialog.WorkbenchChooseDialogPresenter
      • info.magnolia.ui.admincentral.dialog.WorkbenchChooseDialogPresenterFactory
      • info.magnolia.ui.admincentral.dialog.WorkbenchChooseDialogView

      Proposed package structure:

      • info.magnolia.ui.contentapp
      • info.magnolia.ui.contentapp.workbench
      • info.magnolia.ui.contentapp.item
      • info.magnolia.ui.contentapp.item.action
      • info.magnolia.ui.contentapp.choosedialog

        Acceptance criteria

              dlipp Daniel Lipp
              tmattsson Tobias Mattsson
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoR