Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-134145

Upgrades for modules should be registered before PORTL INITIALIZED event on startup

    Details

    • Type: Bug
    • Status: Verified
    • Resolution: Unresolved
    • Affects Version/s: 7.2.X, 7.3.X, Master
    • Fix Version/s: None
    • Labels:
      None
    • Fix Priority:
      3

      Description

      We have define a service lifecycle with different events:
      https://github.com/liferay/liferay-portal/blob/master/portal-kernel/src/com/liferay/portal/kernel/module/framework/ModuleServiceLifecycle.java

      We should ensure that all the upgrades run and the database is ready in one of the early events. Before PORTAL INITIALIZED ideally, if that's not possible, before PORTLETS INITIALIZED.

      That helps users and customers to be sure that the database is ready so they can develop component that require it and can be executed in a later stage.

      With the property upgrade.database.auto.run is set to true, they are registered on time, that's not the case on a regular startup.

        Attachments

          Activity

            People

            Assignee:
            team-upgrades Product Team Upgrades
            Reporter:
            alberto.chaparro Alberto Chaparro
            Participants of an Issue:
            Recent user:
            Alberto Chaparro
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Days since last comment:
              13 weeks, 5 days ago

                Packages

                Version Package