You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.
Currently the tck sig test requires running a separate java command, passing quite some arguments. Can we automate the sig test run and include it as part of the regular test run, so all the testing can be done in one shot?
We could add it to build.xml as part of the run target, or add a testng test that does the signature verification. The latter seems a better choice.
Comment 1 ScottKurz 2015-05-22 13:47:50 UTC
For this one the automation is already in place. The remaining task is to update the TCK doc to make users aware of this and formally point out that this is a legitimate way to run the TCK.
Will do this only in the 1.1 TCK doc.
The text was updated successfully, but these errors were encountered:
One note I'll add while I'm thinking about it.. the IBM JRE has a different location of the rt.jar (and some related classes...I forget which). The net of it is that the instructions should be customized for Oracle vs IBM JREs.
Pasting from:
https://java.net/bugzilla/show_bug.cgi?id=4812
cf126330 2013-03-19 01:59:44 UTC
Currently the tck sig test requires running a separate java command, passing quite some arguments. Can we automate the sig test run and include it as part of the regular test run, so all the testing can be done in one shot?
We could add it to build.xml as part of the run target, or add a testng test that does the signature verification. The latter seems a better choice.
Comment 1 ScottKurz 2015-05-22 13:47:50 UTC
For this one the automation is already in place. The remaining task is to update the TCK doc to make users aware of this and formally point out that this is a legitimate way to run the TCK.
Will do this only in the 1.1 TCK doc.
The text was updated successfully, but these errors were encountered: