Warning about unavailable LPS
Written By
Viktória Gyömbér
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
- I received a long list of missing LPS/LPE after deploying a new hotfix.
Resolution
- This is only a fix pack documentation error, that can be ignored.
- The portal-impl.jar contains a list of fixed issues in its META-INF/MANIFEST.MF under the key
Liferay-Portal-Fixed-Issues, which patching tool uses to know what fixes you already have installed.
Hotfixes will also include an update to portal-impl.jar where this list is updated to match the list of fixes in the original fp20 + the list of new issues that are fixed by the new hotfix. Thus, when applying the fix, the next time you run the patching tool and it runs a comparison against portal-impl.jar, it will know if you've got all the fixes from the last hotfix and warn you if there's a mismatch.
Something went wrong with recording what issues were fixed in the fix packs that were released on the date mentioned in the Help Center article, and we later resolved the issue for later fix packs and hotfixes.
This results in the following discrepancy: if we check fixpack_documentation.xml for fp20, fixes like e.g. LPS-142848 are not included. However, it is technically fixed, and so we make sure that the MANIFEST.MF for a hotfix based on fp20 includes it.
Did this article resolve your issue ?