legacy-knowledge-base
公開されました Sep. 10, 2025

'Unresolved Requirement' error for a custom module post upgrading DXP 7.4 from U24 to U92

written-by

Anushka Tiwari

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

learn-legacy-article-disclaimer-text

Issue

  • Receiving the 'Unresolved Requirement' error below for a custom module post upgrading DXP 7.4 from u24 to u92:
    ERROR [Framework Event Dispatcher: Equinox Container: a66dab4b-cb78-460e-aa7f-8ea2748a79be][Framework:47] FrameworkEvent ERROR

    com.liferay.portal.kernel.log.LogSanitizerException: org.osgi.framework.BundleException: Could not resolve module: jp.co.cardif.theme.helper.contributor [1725]_ Unresolved requirement: Import-Package: com.liferay.asset.kernel.model; version="[8.0.0,9.0.0)"_ [Sanitized]

    at org.eclipse.osgi.container.Module.start(Module.java:444) ~[org.eclipse.osgi.jar:?]

Environment

  • Liferay DXP 7.4

Resolution

  • First, after upgrading, need to update the module version. Use this tool to identify module version changes between major Liferay DXP releases. Module Version Changes
  • Next, review the pom.xml, and verify the version in the below property:
    <groupId>com.liferay.portal</groupId>
    <artifactId>com.liferay.portal.kernel</artifactId>
    <!-- <version>2.6.0</version> -->
    <version>50.0.1</version>
    <scope>provided</scope>
    </dependency>
    <!-- Liferay -->
  • Update the version and change the above file into the below configuration:
    <dependency>
    <groupId>com.liferay.portal</groupId>
    <artifactId>com.liferay.portal.kernel</artifactId>
    <version>121.0.0</version>
    <scope>provided</scope>
    </dependency>
  • The current update version needs to be updated to 121.0.0 which is causing this issue.

Additional Information

did-this-article-resolve-your-issue

legacy-knowledge-base