...

    <plugin>

    <groupId>org.netbeans.tools</groupId>

    <artifactId>sigtest-maven-plugin</artifactId>

    <version>1.5</version>

    </plugin>

The source for the sigtest plugin can be found here: https://github.com/jtulach/netbeans-apitest

To run the signature test, use a pom file like that found in https://github.com/eclipse-ee4j/cdi-tck/blob/master/impl/src/main/resources/sigtest-pom.xml and shown here:

<?xml version="1.0"?>

<!-- Sample maven pom to verify signatures -->

<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 http://maven.apache.org/maven-v4_0_0.xsd">

  <modelVersion>4.0.0</modelVersion>

  <!-- For access to staging repos, add -Pstaging -->

  <parent>

    <groupId>org.eclipse.ee4j</groupId>

    <artifactId>project</artifactId>

    <version>1.0.6</version>

  </parent>



  <groupId>jakarta.enterprise</groupId>

  <artifactId>cdi-tck-sigtest</artifactId>

  <version>4.0</version>

  <name>CDI TCK Signature Tests</name>

  <description>CDI TCK Signature test validation of CDI dependent API jars</description>

  <properties>

    <!-- Set the api jar artifact versions here -->

    <annotation.api.version>2.1.0</annotation.api.version>

    <atinject.api.version>2.0.1</atinject.api.version>

    <interceptor.api.version>2.1.0</interceptor.api.version>

    <el.api.version>5.0.0</el.api.version>

    <cdi.api.version>4.0.1</cdi.api.version>

  </properties>



  <!-- Set the api jar artifact dependencies here -->

  <dependencies>

    <dependency>

      <groupId>jakarta.annotation</groupId>

      <artifactId>jakarta.annotation-api</artifactId>

      <version>${annotation.api.version}</version>

    </dependency>

    <dependency>

      <groupId>jakarta.el</groupId>

      <artifactId>jakarta.el-api</artifactId>

      <version>${el.api.version}</version>

    </dependency>

    <dependency>

      <groupId>jakarta.interceptor</groupId>

      <artifactId>jakarta.interceptor-api</artifactId>

      <version>${interceptor.api.version}</version>

    </dependency>

    <dependency>

      <groupId>jakarta.inject</groupId>

      <artifactId>jakarta.inject-api</artifactId>

      <version>${atinject.api.version}</version>

    </dependency>

    <dependency>

      <groupId>jakarta.enterprise</groupId>

      <artifactId>jakarta.enterprise.lang-model</artifactId>

      <version>${cdi.api.version}</version>

    </dependency>

    <dependency>

      <groupId>jakarta.enterprise</groupId>

      <artifactId>jakarta.enterprise.cdi-api</artifactId>

      <version>${cdi.api.version}</version>

    </dependency>

  </dependencies>



  <build>

    <plugins>

      <plugin>

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-dependency-plugin</artifactId>

        <executions>

          <execution>

            <id>unpack-dependencies</id>

            <phase>package</phase>

            <goals>

              <goal>unpack-dependencies</goal>

            </goals>

            <configuration>

              <stripVersion>true</stripVersion>

              <overWriteReleases>true</overWriteReleases>

              <outputDirectory>target/classes</outputDirectory>

            </configuration>

          </execution>

        </executions>

      </plugin>

      <plugin>

        <groupId>org.netbeans.tools</groupId>

        <artifactId>sigtest-maven-plugin</artifactId>

        <version>1.5</version>

        <executions>

          <execution>

            <id>sigtest</id>

            <phase>verify</phase>

            <goals>

              <goal>check</goal>

            </goals>

          </execution>

        </executions>

        <configuration>

          <sigfile>cdi-api-jdk11.sig</sigfile>

          <packages>jakarta.decorator,jakarta.enterprise,jakarta.interceptor</packages>

          <classes>target/classes</classes>

          <report>cdi-sig-report.txt</report>

        </configuration>

      </plugin>

    </plugins>

  </build>

</project>

Your version should specify the dependencies on these jars as used in your compatible implementation.

Scotts-iMacPro:resources starksm$ mvn -f sigtest-pom.xml verify
[INFO] Scanning for projects...
[INFO]
[INFO] -----------------< jakarta.enterprise:cdi-tck-sigtest >-----------------
[INFO] Building CDI TCK Signature Tests 4.0
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
...
[INFO] --- sigtest-maven-plugin:1.5:check (sigtest) @ cdi-tck-sigtest ---
[INFO] Packages: jakarta.decorator,jakarta.enterprise
[INFO] SignatureTest report
Base version: 4.0.0-SNAPSHOT
Tested version: 4.0
Check mode: bin [throws removed]
Constant checking: on

Warning: The return type java.lang.reflect.Member can't be resolved
Warning: The return type java.lang.reflect.Member can't be resolved
Warning: The return type java.lang.reflect.Member can't be resolved


[INFO] /Users/starksm/Dev/JBoss/Jakarta/cdi-tck/impl/src/main/resources/cdi-sig-report.txt: 0 failures in /Users/starksm/Dev/JBoss/Jakarta/cdi-tck/impl/src/main/resources/cdi-api-jdk11.sig
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  1.941 s
[INFO] Finished at: 2021-12-13T11:38:06-06:00
[INFO] ------------------------------------------------------------------------

You can ignore the following warnings: "The return type java.lang.reflect.Member can't be resolved"

The important thing is that the mvn version shows "BUILD SUCCESS".

Another example that just specifies a compatible implementation test as the dependency to validate the API artifact signatures from the transitive dependencies is pom file like that found in https://github.com/eclipse-ee4j/cdi-tck/blob/master/impl/src/main/resources/sigtest-weld-pom.xml and shown here:

<?xml version="1.0"?>

<!-- Sample maven pom to verify signatures using only the weld-core-imp artifiact and its dependencies -->

<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 http://maven.apache.org/maven-v4_0_0.xsd">

  <modelVersion>4.0.0</modelVersion>

  <!-- For access to staging repos, add -Pstaging -->

  <parent>

    <groupId>org.eclipse.ee4j</groupId>

    <artifactId>project</artifactId>

    <version>1.0.6</version>

  </parent>



  <groupId>jakarta.enterprise</groupId>

  <artifactId>cdi-tck-weld-sigtest</artifactId>

  <version>4.0</version>

  <name>CDI TCK Signature Tests</name>

  <description>CDI TCK Signature test validation of CDI dependent API jars</description>

  <properties>

    <!-- Set the Weld version to test -->

    <weld.version>5.0.0.CR2</weld.version>

  </properties>



  <!-- Set the api jar artifact dependencies here -->

  <dependencies>

    <dependency>

      <groupId>org.jboss.weld</groupId>

      <artifactId>weld-core-impl</artifactId>

      <version>${weld.version}</version>

    </dependency>

  </dependencies>



  <build>

    <plugins>

      <plugin>

        <groupId>org.apache.maven.plugins</groupId>

        <artifactId>maven-dependency-plugin</artifactId>

        <executions>

          <execution>

            <id>unpack-dependencies</id>

            <phase>package</phase>

            <goals>

              <goal>unpack-dependencies</goal>

            </goals>

            <configuration>

              <outputDirectory>target/classes</outputDirectory>

              <overWriteReleases>false</overWriteReleases>

              <overWriteSnapshots>false</overWriteSnapshots>

              <overWriteIfNewer>true</overWriteIfNewer>

            </configuration>

          </execution>

        </executions>

      </plugin>

      <plugin>

        <groupId>org.netbeans.tools</groupId>

        <artifactId>sigtest-maven-plugin</artifactId>

        <version>1.5</version>

        <executions>

          <execution>

            <id>sigtest</id>

            <phase>verify</phase>

            <goals>

              <goal>check</goal>

            </goals>

          </execution>

        </executions>

        <configuration>

          <sigfile>cdi-api-jdk11.sig</sigfile>

          <packages>jakarta.decorator,jakarta.enterprise,jakarta.interceptor</packages>

          <classes>target/classes</classes>

          <report>cdi-sig-report.txt</report>

        </configuration>

      </plugin>

    </plugins>

  </build>

</project>

cd jakartacdi/tck/weld/jboss-tck-runner

Then execute the Maven life cycle through the test phase:

mvn test

Without any command-line flags, the test suite is run in standalone mode (activating weld-embedded Maven profile), which means that any test within the integration, javaee-full and SE TestNG group is excluded. This mode uses the Weld EE Embedded Arquillian container adapter to invoke the test within a mock Jakarta EE life cycle and capture the results of the test. However, passing the suite in this mode is not sufficient to pass the TCK as a whole. The suite must be passed while executing using the in-container mode.

To execute tests within Core and EE parts of the specification you need to use in-container mode with the JBoss TCK runner, you first have to setup WildFly as described in the Running the TCK against Weld and WildFly callout.

Then, execute the TCK runner with Maven as follows:

mvn test -Dincontainer

The presence of the incontainer property activates an incontainer Maven profile. This time, all the tests except the tests within SE TestNG group are executed.

In order to run tests appropriate to the Jakarta EE Web Profile execute:

mvn test -Dincontainer=webprofile

To specify particular TCK version:

mvn test -Dincontainer -Dcdi.tck.version=4.0.1

The Arquillian will also start and stop the application server automatically (provided a managed Arqullian container adapter is used).

Since Arquillian in-container tests are executed in a remote JVM, the results of the test must be communicated back to the runner over a container-supported protocol. The TCK utilizes servlet-based protocol (communication over HTTP).

To execute full TCK testsuite you have to run tests within SE group as well. SE tests make use of Arquillian container SE. This way the tests are executed in a separate JVM instance with isolated and configurable classpath. The Arquillian container does not start CDI container in any way - this is still done directly in the tests using CDI SE bootstrap API and jakarta.enterprise.inject.se.SeContainerInitializer. In order to run SE TCK tests in Weld, you need to execute "weld-se" Maven profile from the JBoss TCK runner POM file as follows:

---
mvn test -Dincontainer=se
---

The profile needs to provide RI dependencies as well as Arquillian settings (arquillian.xml). These two need to be stored into a directory so that Arquillian container can then be instructed to pick them up. In Weld, this orchestration is done using maven-dependency-plugin along with maven-surefire-plugin.

The feature just described is activated in the Arquillian configuration file (Section 4.2, “Arquillian settings”). In order to export the test archive you’ll have to add the deploymentExportPath property element inside engine element and assign a relative or absolute directory where the test archive should be exported, e.g.:

            <engine>

                <property name="deploymentExportPath">target/</property>

            </engine>

Arquillian will export the archive to that location for any test you run.

To enable the export for just a single test, use the VM argument arquillian.deploymentExportPath:

-Darquillian.deploymentExportPath=target/deployments/

cd jakartacdi/tck/weld/lang-model-tck

Then, execute the TCK runner with Maven as follows:

mvn test

The TCK can be executed in any IDE for which there is a TestNG plugin available. Running a test from the CDI TCK test suite using the Eclipse TestNG plugin is almost as simple as running any other TestNG test. You can also use the plugin to debug a test, which is described in the next chapter.

Before running a test from the TCK test suite in Eclipse, you must have the Eclipse TestNG plugin and either the m2e plugin or an Eclipse project generated using the Maven 2 Eclipse plugin (maven-eclipse-plugin). Refer to Section 3.3, “Eclipse Plugins” for more information on these plugins.

With the m2e plugin installed, Eclipse should recognize the CDI TCK projects as valid Eclipse projects (or any Weld project for that matter). Import them into the Eclipse workspace at this time. You should also import the Weld projects if you want to debug into that code, which is covered later.

cd tck
mvn clean eclipse:clean eclipse:eclipse -DdownloadSources -DdownloadJavadocs
cd ../weld
mvn clean eclipse:clean eclipse:eclipse -DdownloadSources -DdownloadJavadocs

In order to debug an integration test, or any test run using in-container mode, the test must be configured to run in-container, as described in Section 9.4, “Running integration tests”, and you must attach the IDE debugger to the container. That puts the debugger on both sides of the fence, so to speak.

Since setting up a test to run in-container has already been covered, we’ll look at how to attach the IDE debugger to the container, and then move on launching the test in debug mode.