The Annotation signature test class and related files in
https://github.com/jakartaee/common-annotations-api/tree/master/tck/src/main/java/ee/jakarta/tck/annotations/signaturetest were duplicated/copied and modified from
https://github.com/jakartaee/platform-tck/tree/tckrefactor/signaturetest/src/main/java/com/sun/ts/tests/signaturetest/caj so as to migrate the test to the specification repository and to avoid the dependency on platform TCK signature test module which was
not available in maven then yet.
This CAJSigTestIT.java and other files is majorly used to invoke the “com.sun.tdk.signaturetest.SignatureTest” in signature test plugin
as here using the right parameters. I agree that it could be more simplified. The classes and packages are tested in static and reflective modes
here.
IMO if the signature test plugin has the option to run “com.sun.tdk.signaturetest.SignatureTest” as maven targets with the right parameters as it currently does, we could use the
plugin directly. I have created the issue
https://github.com/eclipse-ee4j/jakartaee-tck-tools/issues/29 earlier to track this enhancement.
Thanks,
Alwin Joseph
From:
Arjan Tijms <arjan.tijms@xxxxxxxxxxx>
Date: Monday, 18 March 2024 at 8:41 PM
To: Alwin Joseph <alwin.joseph@xxxxxxxxxx>
Cc: Scott Marlow <smarlow@xxxxxxxxxx>, jakartaee-tck developer discussions <jakartaee-tck-dev@xxxxxxxxxxx>, Gurunandan Rao <gurunandan.rao@xxxxxxxxxx>, Edward Burns <Edward.Burns@xxxxxxxxxxxxx>, Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>, Lukas
Jungmann <lukas.jungmann@xxxxxxxxxx>
Subject: Re: [External] : Re: Official Annotations 3.0.0 TCK?
Hi
Would it not be easier if the runner pom just:
1. Downloaded the GlassFish distribution used for testing
2. Defined a property to point to the commons API jar file within the just downloaded GlassFish
3. Run the Signature test plugin with the previously generated sig file and the just defined property as input?
Hi,
Thanks everyone for the answers!
|