Add a "thin" Maven profile for each Liferay Faces archetype in order to support JSF thin WAR deployment

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: None
• Fix Version/s: adf-archetype-5.1.0, alloy-archetype-5.1.0, bootsfaces-archetype-5.1.0, butterfaces-archetype-5.1.0, jsf-archetype-5.1.0, primefaces-archetype-5.1.0, richfaces-archetype-5.1.0, alloy-archetype-6.1.0, bootsfaces-archetype-6.1.0, butterfaces-archetype-6.1.0, jsf-archetype-6.1.0, primefaces-archetype-6.1.0, richfaces-archetype-6.1.0, adf-archetype-6.1.0
• Component/s: ADF Archetype, Alloy Archetype, BootsFaces Archetype, ButterFaces Archetype, JSF Archetype, PrimeFaces Archetype, RichFaces Archetype
• Labels: None

This issue is related to FACES-3024 in that it relies on the ability to deploy Liferay Faces dependencies as OSGi modules in $LIFERAY_HOME/osgi/modules.

When this new feature is implemented, it will be possible to generate a JSF portlet project from a Maven archetype and build it with the thin profile. The result will be a WAR artifact that is much smaller in size because it contains fewer (if any) JSF dependencies in the WEB-INF/lib folder inside the archive.

For example:

mvn archetype:generate -B \
  -DarchetypeGroupId=com.liferay.faces.archetype \
  -DarchetypeArtifactId=com.liferay.faces.archetype.jsf.portlet \
  -DarchetypeVersion=5.1.0\
  -DgroupId=com.mycompany \
  -DartifactId=com.mycompany.my.jsf.portlet \
  -Dversion=1.0.0 \
  -Dpackage=com.mycompany

cd com.mycompany.my.jsf.portlet

mvn -P thin clean package

Note that if the thin profile is not specified, then the WAR will be thick, meaning it has all necessary JSF dependencies in the WEB-INF/lib folder inside the archive.