lutece-migration-v8

Migrating a Lutece v7 plugin to v8 involves a phase-driven, task-based workflow of 15 defined phases with blocking dependencies and mandatory per-phase verification to guarantee a consistent upgrade. You initialize the Phase 0 task, then progress sequentially through subsequent phases.

The javax to jakarta package rename during a Lutece migration is one of the 15 phases that systematically updates import statements and references across plugin code. This task is explicitly blocked by prior phases and requires per-phase verification to ensure all Spring and REST dependencies are cleanly updated.

Yes, the Lutece v7 to v8 migration process handles Spring to CDI migration, including CDI wiring, as part of its comprehensive scope. This task is integrated into the 15-phase workflow with explicit blockedBy dependencies to ensure it executes in the correct order alongside REST and template updates.

Yes, you can use this phase-driven workflow for migrating Lutece modules and libraries, as the process is scalable and repeatable for plugins, modules, and libraries. The 15-phase structure with blocking dependencies and mandatory verifications ensures consistent upgrades across different types of Lutece components.

The best way to ensure a consistent Lutece v8 upgrade across multiple plugins is to use a phase-driven, task-based workflow with 15 defined phases, explicit blockedBy dependencies, and mandatory per-phase verification. This scalable approach guarantees a clean upgrade for plugins, modules, and libraries.

The Lutece migration workflow enforces blockedBy dependencies between phases to prevent out-of-order execution and guarantee a consistent upgrade. By requiring mandatory per-phase verification before progressing, the 15-phase structure ensures tasks like POM updates, javax to jakarta renames, and CDI wiring are completed correctly.