Details
-
Bug
-
Status: Closed
-
Resolution: Fixed
-
7.2.10 DXP FP11, 7.2.X, Master
-
7.3.x, 7.2.x
-
Committed
-
4
-
Regression Bug
Description
If you deploy a fragment bundle, it never changes to resolved state, it remains in "installed" state.
Steps to reproduce
- Deploy the attached com.liferay.blade.module.jsp.override-1.0.0.jar
osgi fragment module. (It was created from the blade samples)
- Connect to the gogo shell and execute lb |grep -v Active
- Check the state of the deployed module:
- Expected behavior: The module is in "Resolved" status
- Wrong behavior: The module is in "Installed" status
- Expected behavior: The module is in "Resolved" status
- Additional verification: check that the unsolved dependency should be satisfied
- Execute diag <bundleId> to get the missing dependency of the osgi fragment
- Execute lb -s com.liferay.login.web to get the version of the host module
- Verify that the fragment expects any version between 1.0.0 and 7.0.0, and the com.liferay.login.web module has a matching one.
Workaround
You can apply following steps to solve the wrong dependency:
- Stop the application server
- Delete the osgi/state folder content
- Start the application server
Attachments
Issue Links
- is caused by
-
LPS-122008 Simplify file install header parsing
-
- Closed
-
- is duplicated by
-
LPS-129938 Liferay Module Project Fragment remains installed not resolved
- Closed