Rename groupId and artifactId for all modules according to the OSGi naming convention

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: None
• Fix Version/s: alloy-1.0.0, alloy-2.0.0, alloy-3.0.0, generator-1.0.0, portal-1.0.0, portal-2.0.0, portal-3.0.0, util-1.0.0, util-2.0.0, util-3.0.0, bridge-impl-2.0.0, bridge-impl-3.0.0, metal-1.0.0, bridge-ext-1.0.0, bridge-ext-2.0.0, bridge-ext-3.0.0, bridge-ext-5.0.0, facesbridge-api-5.0.0, bridge-api-2.0.0, bridge-api-3.0.0, bridge-api-4.0.0, showcase-2.0.0, facesbridge-tck-5.0.0, bridge-impl-4.0.0, bridge-impl-5.0.0, showcase-3.0.0, facesbridge-tck-2.0.0, facesbridge-tck-3.0.0, facesbridge-tck-4.0.0
• Component/s: FacesBridge API, FacesBridge TCK, JSF Showcase, Liferay Faces Alloy / Showcase / Tests, Liferay Faces Bridge API, Liferay Faces Bridge Ext, Liferay Faces Bridge Impl / Demos / Tests, Liferay Faces Generator, Liferay Faces Metal / Showcase / Tests, Liferay Faces Portal / Demos / Tests, Liferay Faces Util
• Labels: None

Liferay Portal 7.0 utilizes OSGi to achieve modularity and the portal's dependency artifact filenames follow the OSGi file naming convention using Bundle-SymbolicName.

Although the Liferay Faces artifacts are currently designed to be embedded dependencies (inside the WEB-INF/lib directory of a WAR), this task involves adopting the OSGi bundle file naming convention for artifactId in pom.xml descriptors in order to be consistent with the rest of the company. It will also help to guide us towards the goal of having the Liferay Faces dependency artifacts to be separately deployable OSGi bundles.

In addition groupId will be renamed to one of the following:

• com.liferay.faces
• com.liferay.faces.demo
• com.liferay.faces.issue
• com.liferay.faces.support
• com.liferay.faces.test