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
Update signature map files for Jakarta EE 10 #767
Comments
https://gist.github.com/scottmarlow/7918fd62667363ff8d980499d9ca9298 shows the failures I get locally trying to generate signature test map files on JDK11 |
The https://github.com/scottmarlow/jakartaee-tck/tree/build_signatures branch reflects changes that fix the failures mentioned in previous comment. I am testing locally with WildFly Preview (master branch) which reflects the EE 9.1 SPEC APIs (so some signature test failures are expected). Note that https://github.com/scottmarlow/jakartaee-tck/tree/build_signatures also includes a locally built sigtest tool using the https://github.com/scottmarlow/netbeans-apitest/tree/sync_with_originalrepo_master tree, which is a work in progress that will be contributed soon (when complete). |
Some local WildFly Preview (Jakarta EE 9.1) TCK test results (from_ejb) with this change:
build_signatures/3 test results show about the same:
|
@scottmarlow - PR #778 is already merged, shall we close the issue? |
https://gist.github.com/scottmarlow/477c36a60c109b356b99c5631705819a has an initial attempt at adding a
docker/build_signatures.sh
script for updating the signature test files. The initial work was done earlier this year for EE 9.1 but we ran out of time in the schedule, so it didn't get completed.Running the script should update the local signature map files so that a pull request can be generated while running on Java SE 11.
We should also switch from
*.se8
signature map files to*.se11
files.The text was updated successfully, but these errors were encountered: