Could not resolve module - Unresolved requirement error
How To articles are not official guidelines or officially
supporteddocumentation. They are community-contributed content and may
not alwaysreflect the latest updates to Liferay DXP. We welcome your
feedback toimprove How to articles!
While we make every effort to ensure this Knowledge Base is accurate,
itmay not always reflect the most recent updates or official
guidelines.We appreciate your understanding and encourage you to reach
out with anyfeedback or concerns.
Legacy Article
You are viewing an article from our legacy
"FastTrack"publication program, made available for
informational purposes. Articlesin this program were published without a
requirement for independentediting or verification and are provided
"as is" withoutguarantee.
Before using any information from this article, independently verify
itssuitability for your situation and project.
Issue
- Getting below error while deploying the ext module in the Liferay instance
org.osgi.framework.BundleException: Could not resolve module: com.liferay.journal.service [1099]_ Unresolved requirement: Import-Package: com.liferay.journal.model; version="[3.0.0,3.1.0)"_ [Sanitized]
Resolution
-
Steps to replicate the behavior:
- Create a new ext project in LDS and select the Original module name as "com.liferay.journal.service"
- Add a java file in the EXT project.
- Build a module and deploy it on the server.
-
Observed behavior: The above error is thrown.
-
Additional steps to resolve the issue:
- Update the module version in the build.gradle as per your Liferay bundle.
-
For eg: DXP 7.2 dxp-2 bundle: In build.gradle,
originalModule group: "com.liferay", name: "com.liferay.journal.service", version: '5.0.41'
-
- Rebuild it
- Deploy it in the server
- Note: Have to deactivate the original module which is available by default in the portal.
-
The reason behind this is: You have to point out the module version based on the target platform.
-
Additionally, since EXT projects are deprecated from DXP, it's never recommended to create a custom class in EXT unless there is absolutely no other way to accomplish your task.
Did this article resolve your issue ?
