Ezpublish Legacy Installer Laravel Package

Product Decisions This Supports

• Legacy platform maintenance vs. migration: Informs the choice between keeping eZ Publish Legacy (4.x/5.x) running with Composer-managed extensions and funding migration to Ibexa/eZ Platform. Composer 2 support lowers the cost and risk of the “keep the lights on” option for another planning cycle.
• Security patching roadmap: Composer 2 is required by much current PHP tooling and dependency workflows. This release removes a blocker to running supported Composer versions and applying upstream library updates on legacy sites.
• Build vs. buy / reuse: For teams operating legacy eZ Publish with community or custom extensions, adopting this installer avoids bespoke install scripts and gives reproducible composer install behavior; building an in-house equivalent is rarely justified.
• Use cases: Maintaining legacy eZ Publish sites that still depend on legacy extensions; modernizing CI pipelines to Composer 2; audit/compliance work requiring current dependency tooling on legacy applications.

When to Consider This Package

Consider it when:

• You run eZ Publish Legacy (4.x/5.x) and install legacy extensions via Composer.
• You are upgrading build tooling to Composer 2 and need the installer to remain compatible.
• You need repeatable, version-pinned installs of legacy extensions across environments.
• You are in a maintenance window and want the lowest-risk path to supported tooling without a platform migration.

Look elsewhere when:

• You are on Ibexa DXP / eZ Platform (not legacy) — use native Composer/recipes instead.
• You have migrated off eZ Publish Legacy or do not manage legacy extensions through Composer.
• You require active feature development or long-term vendor support; this is a maintenance-oriented installer for a legacy platform.
• Your constraint is PHP runtime support rather than Composer version — verify PHP compatibility separately.

How to Pitch It (Stakeholders)

Executives: This is a small, low-cost compatibility update that extends the life of existing eZ Publish Legacy investments. Composer 2 support helps keep legacy sites on supported dependency tooling, reducing security and audit risk while migration is planned or deferred. It does not add product features; treat it as risk reduction, not roadmap acceleration.

Engineering: v2.1.0 is an additive, non-breaking release adding Composer 2 support. It allows legacy projects to move off Composer 1 without changing extension installation behavior. Validate in a staging build first, confirm PHP version compatibility, and pin the version. This is a maintenance signal: plan eventual migration off legacy rather than expecting new capabilities.