Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the sigtest Release to allow for new JVM's #24

Merged
merged 2 commits into from
Feb 15, 2024

Conversation

jamezp
Copy link
Contributor

@jamezp jamezp commented Feb 14, 2024

The current way of only using data from the version this project was compiled on does not work when you want to run against newer JVM's. For example errors like Fatal error: class java.lang.annotation.Annotation not found are reported because the com.sun.tdk.signaturetest.classpath.Release cannot be found.

This change uses the local ${java.home}/lib/ct.sym to determine the signature files.

resolves #22

…ository.

Signed-off-by: James R. Perkins <jperkins@redhat.com>
…uire a minimum of Java SE 17 for testing and add Java 17 tests.

Signed-off-by: James R. Perkins <jperkins@redhat.com>
@scottmarlow
Copy link
Member

I built the change locally and verified that the EE 10 Platform TCK signature tests still work correctly with this change on Java SE 11/17/21.

@starksm64 starksm64 merged commit f468429 into eclipse-ee4j:master Feb 15, 2024
1 check passed
@jamezp jamezp deleted the sig-generation-fix branch February 21, 2024 23:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add Java 17+ support
3 participants