Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-23746

Externalize Legacy bridge

    XMLWordPrintable

Details

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: High High
    • 2015.01, Pollux
    • None
    • None
    • None
    • Externalize Legacy bridge

    Description

      Move Legacy (in Bundle + Core + settings) related code out from eZ Platform kernel, first making the dependency optional and later stop including it completely.

      Requirements:

      • Split out EzPublishLegacyBundle to its own repo, with 2 separate namespaces (use PSR-4 to fix autoloading):
        • eZ\Bundle\EzPublishLegacyBundle
        • eZ\Publish\Core\MVC\Legacy
      • Remove ezpublish-legacy from platform's composer.json (+ implicit by moving legacyBundle out also from kernel repo)
      • Fix legacy leaks
      • Separate cache clearing integration (new stack cache is cleared by legacy when publishing, needs to be done from new stack while avoiding cyclic cache clearing)

      If this is merged before setup wizard work we will need a manual way to install eZ Platform somehow (clean or demo install needs to be defined). Aka minimum: not break BDD which uses demo clean install (no demo content), ideally also not break Demo BDD tests (depends on demo content).

      Attachments

        Activity

          People

            bertrand.dunogier@ibexa.co Bertrand Dunogier
            bertrand.dunogier@ibexa.co Bertrand Dunogier
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: