Details

    • Epic/Theme:
    • Story Points:
      2
    • Fix Priority:
      5

      Description

      Let's say that we have two portlets: a-portlet and b-portlet, where A depends on B.

      Deploying A fails, as is being fully deployed when B is not yet deployed. This is wrong behavior - plugin A should be queued until B is deployed.

      Example:
      Deploy "a-portlet" and wait until you see

      INFO [HotDeployUtil:156] Queueing a-portlet for deploy because it is missing b-portlet
      ...
      # FooLocalServiceImpl(): null
      

      in the console. So, although the "a-portlet" is still queued, the constructor of the FooLocalServiceImpl (from A) is called. Deploying b-portlet later does not change anything.

        Attachments

          Activity

            People

            • Assignee:
              sharry.shi Sharry Shi
              Reporter:
              igor.spasic Igor Spasic
              Participants of an Issue:
              Recent user:
              Esther Sanz
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                4 years, 19 weeks, 2 days ago