The bridge-api manifest contains Specification-Version is "1.0" instead of "2.0.0"

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: bridge-api-2.0.0
• Fix Version/s: bridge-api-2.1.0
• Component/s: Liferay Faces Bridge API
• Labels: None

Bridge TCK TestPage001 (bridgeVersionTest) currently expects/reports the following output:

Correct Specification Title: Portlet 2.0 Bridge for JavaServer Faces 1.2 and correct specification version: 1.0

The reason why is because of the following text in the FacesBridge API pom.xml descriptor:

pom.xml

<Specification-Title>Portlet 2.0 Bridge for JavaServer Faces 1.2</Specification-Title>
<Specification-Vendor>Java Community Process (JSR 329)</Specification-Vendor>
<Specification-Version>1.0</Specification-Version>

This information needs to be updated to the following:

pom.xml

<Specification-Title>Portlet 2.0 Bridge for JavaServer Faces 2.1</Specification-Title>
<Specification-Vendor>Java Community Process (JSR 329)</Specification-Vendor>
<Specification-Version>2.0.0</Specification-Version>

In addition, Bridge TCK TestPage001 (bridgeVersionTest) needs to updated to expect this information.

The reason why the Specification Version is required to be 2.0.0 is because of the following version scheme:

Version	Portlet API	JSF API	JSR
1.0	1.0	1.2	JSR 301
2.0	2.0	1.2	JSR 329
3.0	2.0	2.1	(no JSR ever filed)
4.0	2.0	2.2	(no JSR ever filed)
5.0	3.0	2.2	JSR 378