Scott Marlow

@KyleAure https://github.com/eclipse-ee4j/jakartaee-tck-tools/tree/master/tools/sigtest contains our Jakarta EE fork (thanks to Scott Stark for doing that!). Is this TCK challenge accepted? It would be helpful to have a https://download.eclipse.org/jakartaee/concurrency/3.0/ TCK release with...

> @scottmarlow Thanks for your work on the sigtest plugin. Should we pull the new plugin into the 3.0.x branch and use that for the next service release? I don't...

Quoting from the [TCK Process](https://jakarta.ee/committees/specification/tckprocess/) on how long it should take to resolve a TCK challenge: >Active Resolution > > The failure to resolve a Challenge might prevent an implementation...

@KyleAure it has been a while, any ETA for when the 3.0 service release might be able to happen?

@lukasj do you want to manage this here as a Persistence TCK challenge (needs challenge label) that if accepted, the described tests will be excluded from the Jakarta EE 10...

@beikov since this is approved, I'll merge your change to the https://github.com/jakartaee/platform-tck/tree/tckrefactor (for EE 11 currently) and https://github.com/jakartaee/platform-tck/tree/10.0.x branches (for EE 10) Platform TCK branches where we generate the Persistence...

https://ci.eclipse.org/jakartaee-tck/job/10/job/eftl-standalonetck-build-run-100/117 generated the staged Persistence https://www.eclipse.org/downloads/download.php?file=/ee4j/jakartaee-tck/jakartaee10/staged/eftl/jakarta-persistence-tck-3.1.3.zip which includes the https://github.com/jakartaee/platform-tck/pull/1246 change. https://ci.eclipse.org/jakartaee-tck/job/10/job/eftl-standalonetck-build-run-100/117/testReport/ shows that the staged Persistence TCK 3.1.3 TCK passed all tests with GlassFish which includes EclipseLink. https://ci.eclipse.org/jakartaee-tck/job/10/job/eftl-standalonetck-build-run-100/118/ also...

I think that this issue can be closed now

This challenge can be closed as the updated TCK has been promoted.

> @scottmarlow what is the status of this issue? Is it still relevant? WildFly + Hibernate implementations have already solved this. I think we could close this and reopen it...