Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

During portlet WAR deployment getting unresolved requirement errors

Written By

Koustuv Dhani

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 deploying a spring portlet WAR using JDK 17 or JDK 21, the following deployment error appears in the Liferay logs:
     
    Unresolved requirement: Import-Package: com.liferay.portal.osgi.web.servlet.jsp.compiler; resolution:="optional"_ Unresolved requirement: Import-Package: com.liferay.portal.spring.context; resolution:="optional"_ Unresolved requirement: Require-Capability:osgi.ee; filter:="(osgi.ee=UNKNOWN)"_ [Sanitized]

Environment

  • 2024.Q1

Resolution

  • Liferay DXP uses an OSGi-based framework that requires modules to specify their Java Execution Environment (osgi.ee). However, WAR-based portlets lack this declaration.

  • During deployment, Liferay tries to wrap the WAR as an OSGi bundle but fails due to the missing osgi.ee version, assigning it "UNKNOWN", which leads to deployment errors.

  • To prevent this error,  disable OSGi execution environment validation by adding the following line to the liferay-plugin-package.properties or bnd.bnd file: 
    -noee: true
  • Once the module is redeployed, the deployment should succeed without OSGi validation errors.

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?