jtreg currently provides a `release` file, conceptually similar to that provided in JDK builds. It contains the version number, build-date and checksum (commit-id) for the source used to build the image.
It would be good if the release file contained info for the dependencies used in the build. This would help improve the ability to determine if two builds are effectively equivalent.
For binary-only artifacts, like TestNG, JUnit etc, this could be the checksum of the imported jar file.
For source-or-binary artifacts, like JT Harness, Asm Tools and JCov, this could be info from the `release` file for those components.
It would be good if the release file contained info for the dependencies used in the build. This would help improve the ability to determine if two builds are effectively equivalent.
For binary-only artifacts, like TestNG, JUnit etc, this could be the checksum of the imported jar file.
For source-or-binary artifacts, like JT Harness, Asm Tools and JCov, this could be info from the `release` file for those components.
- relates to
-
CODETOOLS-7902794 Provide a `release` file for JT Harness builds
-
- Resolved
-
-
CODETOOLS-7902795 Provide a "release" file for AsmTools builds
-
- Resolved
-
-
CODETOOLS-7902796 Provide a "release" file for JCov builds
-
- Resolved
-