Uploaded image for project: 'PUBLIC - Liferay IDE'
  1. PUBLIC - Liferay IDE
  2. IDE-2756

Blade update doesn't work properly for a fragment deployment.


    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.1
    • Fix Version/s: 3.1 M1
    • Component/s: blade-cli
    • Labels:
    • Environment:
      JVM: 1.8.0_92 (Oracle Corporation 25.92-b14)
      OS: Mac OS X 10.11.5 x86_64
      Gradle : 2.14
      Groovy : 2.4.4
      Liferay : DXP GA1


      "blade deploy" doesn't deploy a fragment properly and get exceptions or errors.

      Steps to reproduce

      1. Run "blade init workspace"
      2. Navigate to /module folder.
      3. Run " blade create -t fragment -h com.liferay.login.web -H 1.0.5 login-jsp-override "
      4. Navigate to login-jsp-override folder.
      5. Run "chmod 755 gradlew"
      6. Run "blade deploy" and got error_log.txt
      7. Access to gogo shell (e.g telnet localhost 11311)
      8. Type "lb" and you see login-jsp-override bundle's status is "installed"
      9. Type "refresh". The bundle gets deployed and the bundle status turns out "Resolved"
      10. Type "disconnect" and exit gogo shell, then run "blade deploy" again
      11. You'll get error_log2.txt, but the bundle looks like to be deployed and the status turns out to "Resolved"

      Current behavior
      I get errors or exceptions when the fragment is deployed. Also I need to run "refresh" on gogo shell to be deployed.

      Expected behavior
      The bundle status should be "Resolved" at the first deploy without errors or exceptions.




            • Votes:
              0 Vote for this issue
              3 Start watching this issue


              • Created:
                Days since last comment:
                3 years, 15 weeks ago


                Version Package
                3.1 M1