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.

Sign up for GitHub

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

Jump to bottom

Compatibility certification request for Eclipse GlassFish 6.1 RC1, Jakarta EE Platform, 9.1 #334

Closed
10 tasks done
edbratt opened this issue Apr 23, 2021 · 5 comments
Closed
10 tasks done

Compatibility certification request for Eclipse GlassFish 6.1 RC1, Jakarta EE Platform, 9.1 #334

edbratt opened this issue Apr 23, 2021 · 5 comments
Labels
accepted Accepted certification or challenge request certification Compatibility certification request ratified CCR was used to ratify a Specification version
Milestone
Jakarta EE 9.1 CCRs

Comments

@edbratt
Copy link
Contributor

edbratt commented Apr 23, 2021 •
edited 

java version "11.0.7" 2020-04-14 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.7+8-LTS)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.7+8-LTS, mixed mode)

  • Summary of the information for the certification environment, operating system, cloud, ...:
    Apache Derby,
    Linux, CentOS 7

  • By checking this box I acknowledge that the Organization I represent accepts the terms of the EFTL.

  • By checking this box I attest that all TCK requirements have been met, including any compatibility rules.
@edbratt edbratt added the certification Compatibility certification request label Apr 23, 2021
@ivargrimstad
Copy link
Member

ivargrimstad commented Apr 26, 2021 •
edited

The link to the Bean Validation TCK points to version 3.0.0. The SHA-256 matches, so I guess it is just the link text that should be changed from 3.0.1 to 3.0.0?

$ sha256sum beanvalidation-tck-dist-3.0.0.zip c975fd229df0c40947a9f0a69b779ec92bebb3d21e05fdc65fccc1d11ef5525b beanvalidation-tck-dist-3.0.0.zip

Otherwise, everything looks good!

The same comment applies to the other CCRs (#335, #336, #337) as well.

@edbratt
Copy link
Contributor Author

edbratt commented Apr 26, 2021

The link to the Bean Validation TCK points to version 3.0.0. The SHA-256 matches, so I guess it is just the link text that should be changed from 3.0.1 to 3.0.0?

Fixed all four issues. Thanks for spotting that.

@ivargrimstad
Copy link
Member

+1 LGTM

@kwsutter kwsutter mentioned this issue Apr 27, 2021
Merged
14 tasks
@kwsutter
Copy link
Contributor

LGTM as well! +1

@kwsutter kwsutter added the accepted Accepted certification or challenge request label Apr 29, 2021
@scottmarlow
Copy link
Contributor

👍

@kwsutter kwsutter added the EE9.1 label May 5, 2021
@kwsutter kwsutter added this to the Jakarta EE 9.1 CCR milestone May 6, 2021
@kwsutter kwsutter added ratified CCR was used to ratify a Specification version and removed EE9.1 labels May 6, 2021
@scottmarlow scottmarlow mentioned this issue Jun 23, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
accepted Accepted certification or challenge request certification Compatibility certification request ratified CCR was used to ratify a Specification version
Projects
None yet
Milestone
Jakarta EE 9.1 CCRs
Development

No branches or pull requests
4 participants
@ivargrimstad @scottmarlow @kwsutter @edbratt