Util's PORTLET_API incorrectly reports Portlet 2.1 API version as 1.0 when running in Liferay 7.0 GA5 causing BridgeDependencyVerifier error message

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: util-1.1.0, util-2.1.0, util-3.1.0
• Fix Version/s: util-1.1.1, util-2.1.1, util-3.2.0
• Component/s: Liferay Faces Util
• Labels: None

Due to LPS-74040, the Portlet API jar has been upgraded to use the Portlet 2.1 API jar here: http://search.maven.org/#artifactdetails%7Corg.apache.portals%7Cportlet-api_2.1.0_spec%7C1.0%7Cbundle. Unfortunately, this jar's manifest versions are all set to 1.0, so Util incorrectly detects that the Portlet API version is 1.0. Since BridgeDependencyVerifier relies on this detection, it incorrectly logs an error to indicate that it is running in an Portlet 1.0 environment rather than a Portlet 2.x environment. Note that this error message and bug are benign.

Steps to Reproduce:

1. Checkout the 4.1.0 tag of the bridge-impl project:

    cd $PROJECTS_HOME/liferay-faces-bridge-impl && git checkout 4.1.0
   

2. Build the jsf-applicant-portlet:

    mvn clean install -P mojarra,tomcat,liferay
   

3. Deploy the portlet to Liferay 7.0 GA5

    cp demo/jsf-applicant-portlet/target/*.war $LIFERAY_7_0_GA5_HOME/deploy/com.liferay.faces.demo.jsf.applicant.portlet.war
   

If the bug still exists, the following error message will appear in the logs:

[BridgeDependencyVerifier:57] Liferay Faces Bridge Implementation 4.1.0 (Sep 20, 2017 AD) is designed to be used with Portlet 2.0 but detected 1.0

If the bug is fixed, no error message will appear in Liferay 7.0 GA5 or any older versions of Liferay 7.0 or 6.2.