Legacy Knowledge Base
Published Sep. 10, 2025

Fragments are not getting deployed

Written By

Ankit Gupta

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Steps:
    1) Setup a clean instance of 7.3 fixpack1
    2) Log in to gogo shell and run "lb com.liferay.layout.taglib"
    3) Observe the output, it says : 
    START LEVEL 20
    ID|State |Level|Name
    253|Active | 15|Liferay Layout Taglib (5.3.26)|5.3.26
    which means, Liferay layout taglib version 5.3.26 is active and is available in the OSGi container.
    4) Create a Liferay module fragment for this "Liferay layout taglib version 5.3.26"
    5) Deploy the fragment, log says processing the fragment
    6) Go to gogo shell and run lb
    7) The last bundle will be our fragment in the installed state
    8) Run command "diag {fragment_bundle_id}
    9) Observe the output, it says:
    myfrag2 [1656]
    Unresolved requirement: Fragment-Host: com.liferay.layout.taglib; bundle-version="5.3.26"
    Expected output: Fragment should be in a resolved state with no errors.

Environment

  • Liferay DXP 7.3

Resolution

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base