ee.jakarta.tck.ws.rs.signaturetest.README Maven / Gradle / Ivy

Go to download
The latest signature files are updated in the jaxrsp-api repoitory 
(jaxrs-api/jaxrs-tck/src/main/resources/ee/jakarta/tck/ws/rs/signaturetest)
generated using sigtest-maven-plugin.jar(version 1.4).

The signature tests are run using the sigtest-maven-plugin.jar and the framework avaliable in this folder.



For TCK developers  :-

  1. Generate Signature Files : The signature file will be generated by the TCK team using jaxrs-tck/pom.xml 
  by running 'mvn install -Precord-signature'. The classpath should contain the api jar for which we are generating the signature file.

  The signature file name expected is jakarta.ws.rs.sig_${version} , where version is the api version for which the signature is generated.

  2. Place the required files in the TCK folder :

    All the below files has to be placed in the folder jaxrs-tck/src/main/resources/ee/jakarta/tck/ws/rs/signaturetest, so they are included as part of the TCK jar during the build.

    -The signature file generated from above of the name jakarta.ws.rs.sig_${version}
    -The mapping file will be named sig-test.map, it contains the api to version mapping. This file will be used to pick the right signature file when running the signature test.
    -The package list file will be named sig-test-pkg-list.txt, contains the list of packages tested.



For TCK users (to run the signature test as a Junit test) :-


  1. Set the below system properties correctly :

    jimage.dir //The jdk9+(jdk11 for this release) will be extracted to this location as to use the Java modules in the path.
    optional.tech.packages.to.ignore // The optional package that should be ignored while running the signature test
    signature.sigTestClasspath // the sigTestClasspath that will contain the implementation jar that needs to be tested along with dependent jars.

    For eg:

    ${project.build.directory}/jdk11-bundle
    jakarta.xml.bind
    ${project.build.directory}/glassfish6/glassfish/modules/jakarta.ws.rs-api.jar:${project.build.directory}/glassfish6/glassfish/modules/jakarta.xml.bind-api.jar:${project.build.directory}/jdk11-bundle/java.base:${project.build.directory}/jdk11-bundle/java.rmi:${project.build.directory}/jdk11-bundle/java.sql:${project.build.directory}/jdk11-bundle/java.naming

  2. The signature test alone can be run using below command within jersey-tck/ directory.

  mvn clean verify -Parq-glassfish-managed -Dit.test=ee.jakarta.tck.ws.rs.signaturetest.**