Add profile for testing JakartaEE11 with GlassFish 8 (rebased)

Author: WolfgangHG

.github/workflows/ci.yml

@@ -30,6 +30,12 @@ jobs:
           - jakartaee11,wildfly-jakartaee11-managed
           - glassfish-managed
           - tomee-managed
+          # Build warp with the JakartaEE11 api and run it using the glassfish 8 server:
+          - jakartaee11,glassfish-jakartaee11-managed
+        exclude:
+          # GlassFish 8 does not support Java 17
+          - java: 17
+            container: jakartaee11,glassfish-jakartaee11-managed
     steps:
       - name: Checkout
         uses: actions/checkout@v5

build/ftest-base/pom.xml

@@ -327,6 +327,75 @@
         </dependency>
       </dependencies>
     </profile>
+    <profile>
+      <!-- The GlassFish 8 container supports JakartaEE11.
+           Run this profile only in combination with the profile "jakartaee11" so that arquillian-extension-warp is built using the JakartaEE11 api:
+           mvn clean install -Pjakartaee11,glassfish-jakartaee11-managed
+
+           GlassFish 8 does not support Java 17
+	    -->
+      <id>glassfish-jakartaee11-managed</id>
+      <activation>
+        <property>
+          <name>integration</name>
+          <value>glassfish</value>
+        </property>
+      </activation>
+      <properties>
+        <arquillian.launch.glassfish>true</arquillian.launch.glassfish>
+        <arquillian.container.home>${project.build.directory}/glassfish8</arquillian.container.home>
+        <arquillian.container.distribution>org.glassfish.main.distributions:glassfish:zip:${version.glassfish8}
+        </arquillian.container.distribution>
+        <!-- Relative path to a file that should be made "executable" when the container is started by the arquillian container.
+             Here it is the "asadmin" script (https://github.com/OmniFish-EE/arquillian-container-glassfish/pull/9) -->
+        <arquillian.container.linux.executepermission.file>glassfish8/glassfish/bin/asadmin
+        </arquillian.container.linux.executepermission.file>
+      </properties>
+
+      <!--This profile requires Java 21 to run, as this is required by GlassFish 8 -->
+      <build>
+        <plugins>
+          <plugin>
+            <groupId>org.apache.maven.plugins</groupId>
+            <artifactId>maven-enforcer-plugin</artifactId>
+            <version>3.6.1</version>
+            <executions>
+              <execution>
+                <id>enforce-java</id>
+                <goals>
+                  <goal>enforce</goal>
+                </goals>
+                <configuration>
+                  <rules>
+                    <requireJavaVersion>
+                      <version>21</version>
+                    </requireJavaVersion>
+                  </rules>
+                </configuration>
+              </execution>
+            </executions>
+          </plugin>
+        </plugins>
+      </build>
+
+      <dependencies>
+        <dependency>
+          <groupId>ee.omnifish.arquillian</groupId>
+          <artifactId>arquillian-glassfish-server-managed</artifactId>
+          <version>${version.arquillian.glassfish}</version>
+          <scope>test</scope>
+        </dependency>
+        <!--The dependency on the servlet api must be declared for each profile, see detailed explanation in the
+            test "org.jboss.arquillian.warp.jsf.ftest.lifecycle.TestFacesLifecycleFailurePropagation" in "jsf-ftest" project.
+            Here we use the JBoss implementation instead of the one of GlassFish, as it works as well and is easier to configure.
+          -->
+        <dependency>
+          <groupId>jakarta.servlet</groupId>
+          <artifactId>jakarta.servlet-api</artifactId>
+          <scope>provided</scope>
+        </dependency>
+      </dependencies>
+    </profile>
 
     <profile>
       <!--While executing the tests, Drone uses a locally installed Chrome browser. Combine this profile with any server profile, e.g. "mvnw clean install -Pwildfly-remote,browser-chrome"-->

pom.xml

@@ -107,6 +107,8 @@
          It does not have to match exactly the version bundled with TomEE, but it should be at least the same JakartaEE spec version.-->
     <version.tomee.tomcat>10.1.44</version.tomee.tomcat>
     <version.glassfish>7.0.25</version.glassfish>
+    <!-- GlassFish 8 ist used to test JakartaEE11 features -->
+    <version.glassfish8>8.0.0-M13</version.glassfish8>
     <version.wildfly>38.0.0.Final</version.wildfly>
     <version.wildfly.arquillian.container>5.1.0.Final</version.wildfly.arquillian.container>