Is it possible to separate Liferay module jars and custom jars in osgi/modules directory in the Quarterly Release
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
- After upgrading to Quarterly Release 2023.Q3, Liferay modules are now stored in
osgi/modules directory. Is it possible to separate Liferay module jars and custom jars in osgi/modules directory in the Quarterly Release?
Environment
- Quarterly Release 2023.Q3.x
- Quarterly Release 2023.Q4.0
Resolution
-
In 2023.Q3, the directory
osgi/modulesalso contains Liferay modules. LPS-200065 will move Liferay modules to the directory osgi/portalinstead osgi/modules. This fix is expected to be included in the 2023.Q4.X patch releases.
An alternative resolution to the 2023.Q3 versions is to define your own directory using portal-ext.properties of the form:
module.framework.auto.deploy.dirs=\
${module.framework.client.extensions.dir},\
${module.framework.configs.dir},\
${module.framework.marketplace.dir},\
${module.framework.modules.dir},\
${module.framework.portal.dir},\
${module.framework.war.dir},\
${module.framework.base.dir}/custom
Did this article resolve your issue ?