Legacy Knowledge Base
Published Jun. 30, 2025

Client Extension Build Fails Due to Unresolved Dependency

Written By

Daniel Couso

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

  • When building a Client Extension of type jsImportMapsEntry, the build fails if the Client Extension depends on another Client Extension, because the build cannot resolve the dependency.

Environment

  • Liferay DXP Quarterly Release

Resolution

  • To resolve this issue, explicitly define the dependency in the build.gradle file of the dependent Client Extension. For example, if Client Extension A depends on Client Extension B, add the following line to the build.gradle file of Client Extension A:
    packageRunBuild.dependsOn ':client-extensions:B:packageRunBuild'
  • Replace :client-extensions:B:packageRunBuild with the actual path to Client Extension B, for example :client-extensions:my-module:packageRunBuild.

Additional Information

  • Automatic dependency resolution at the Yarn/NPM level is not supported for Client Extensions.
Did this article resolve your issue ?

Legacy Knowledge Base