<?xml version="1.0" encoding="UTF-8"?>
<!--

    Copyright 2021 OPS4J.

    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.
    You may obtain a copy of the License at

        http://www.apache.org/licenses/LICENSE-2.0

    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.

-->
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">

	<modelVersion>4.0.0</modelVersion>

	<parent>
		<groupId>org.ops4j.pax.web</groupId>
		<artifactId>samples</artifactId>
		<version>11.1.2</version>
		<relativePath>../pom.xml</relativePath>
	</parent>

	<groupId>org.ops4j.pax.web.samples</groupId>
	<artifactId>samples-jsf</artifactId>
	<packaging>pom</packaging>

	<name>OPS4J Pax Web JSF Samples</name>

	<description>
		Since Pax Web 10, we no longer support JSF (because of OSGi/JakartaEE discrepancy).
		However these samples/libraries are used to show how complex OSGi WAB deployments work with Servlet API
		specificaiton (jakarta.servlet.ServletContainerInitializer, web fragments, /META-INF/resources, ...).
		While jakarta.faces.webapp.FacesServlet initializes correctly, TLDs are loaded, we simply can't run
		actual JSF applications, because JSF 4.x simply needs CDI container for beans...
	</description>

	<modules>
		<module>jsf-primefaces-jar</module>
		<module>jsf-primefaces-commons1</module>
		<module>jsf-primefaces-commons2</module>
		<module>jsf-primefaces-commons3</module>
		<module>jsf-primefaces-embedded</module>
		<module>jsf-primefaces-embedded-fragment</module>
	</modules>
</project>
