The artifactId for the JSF API should be javax.faces-api instead of jsf-api

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: liferay-faces-3.0.0-legacy-ga1, liferay-faces-3.0.1-legacy-ga2, liferay-faces-3.0.0-ga1, liferay-faces-3.0.1-ga2, liferay-faces-3.1.0-ga1, liferay-faces-3.1.1-ga2
• Fix Version/s: liferay-faces-3.0.2-legacy-ga3, liferay-faces-3.0.2-ga3, liferay-faces-3.1.2-ga3
• Component/s: Liferay Faces Alloy / Showcase / Tests, Liferay Faces Bridge Impl / Demos / Tests, Liferay Faces Portal / Demos / Tests, Liferay Faces Util
• Labels: None

Correcting this problem involves changing the artifactId for the JSF API from jsf-api to javax.faces-api in all of the pom.xml descriptors.

Background:

Back in the days of JSF 1.2 (dependent on Servlet 2.5), the JSF API was identified like this:

<dependency>
    <groupId>javax.faces</groupId>
    <artifactId>jsf-api</artifactId>
    <version>1.2</version>
</dependency>

But when JSF 2.0 (dependent on Servlet 3.0.1) was released, the artifactId was released not only as jsf-api, but ALSO as javax.faces-api:

<dependency>
    <groupId>javax.faces</groupId>
    <artifactId>javax.faces-api</artifactId>
    <version>2.0</version>
</dependency>

This seems to be the new naming convention of Java EE 6. For example, the servlet-api is now released as javax.servlet-api:

<dependency>
    <groupId>javax.servlet</groupId>
    <artifactId>javax.servlet-api</artifactId>
    <version>3.0.1</version>
</dependency>