Details

      Description

      When we execute upgrade:list after upgrading our portal (just the core not the modules) we can see something like:

      Registered upgrade processes for com.liferay.journal.service 0.0.1
              {fromSchemaVersionString=0.0.0, toSchemaVersionString=1.0.0, upgradeStep=com.liferay.portal.spring.extender.internal.context.Modul[email protected]34f084af}
      

      For a regular user it seems that he/she can com.liferay.journal.service however that it's not true since it needs to install DDM service first.

      My proposal is that we show by default just the upgrades whose upgrade dependencies are covered.

      In addtion it would be nice to have a way to see the rest of modules and the dependencies needed to be covered before upgrading it (for example: upgrade:list -all)

        Attachments

          Activity

            People

            Assignee:
            support-lep@liferay.com SE Support
            Reporter:
            alberto.chaparro Alberto Chaparro
            Recent user:
            Marta Elicegui
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Days since last comment:
              6 years, 8 weeks, 6 days ago

                Packages

                Version Package