Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-4487 Incorporate UI framework improvements into the platform
  3. MGNLUI-4488

Resolve/contemplate potential circular dependency between deprecated and non-deprecated artifacts

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Done
    • Neutral
    • None
    • None
    • None
    • None
    • Basel 151, Basel 152, Basel 153

    Description

      Example:

      • We would like move most of the content app classes to compatibility package.
      • However, we would probably like to keep the location classes (DetailLocation/BrowserLocation) not deprecated.
      • At least DetailLocation, however, references a deprecated class (DetailView).
      • Some deprecated classes though definitely reference DetailLocation.

      We anyway contemplate to keep an unconditional dependency in UI on compatibility artifact, but the situation above requires that the* compatibility layer also depends on the current UI*. This creates a circular dependency which needs to be addressed.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              apchelintcev Aleksandr Pchelintcev
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: