Scott Marlow

> > Does the [RC2 milestone build](https://github.com/eclipse-ee4j/jpa-api/releases/tag/3.1-3.1.0-RC2-RELEASE) have all of the SPEC API changes that went into [3.1.0](https://github.com/eclipse-ee4j/jpa-api/releases/tag/3.1-3.1.0-RELEASE)? > > No. Neither does RC1. If we release a RC3 now...

> > If we release a RC3 now that could allow the Hibernate ORM team to be one of the initial Persistence 3.1 compatible releases. > > Isn't the requirement...

I'm going to comment on #460 after catching up on the contained thread. I'm commenting here with some reference info that is mostly just a links into the Spec and...

> @scottmarlow Right, I understand that. But if you can define a CDI bean of type `EntityManager` with scope `@Dependent`, then that's already an "extended persistence context" with the same...

Sorry for the late comment, if you want to include EJB/JSP tests, please do, but it is not required that you do.

> @scottmarlow Thanks for the feedback. I was under the impression that this WAS a requirement if we wanted to remove these tests from the Platform TCK project. Is that...

Could one of the committers please add the `challenge` label.

@OndroMih would that help avoid the 8 remaining test failures?

I attempted to update https://ci.eclipse.org/jakartaee-tck/job/10/job/jakarta-concurrency-tck-glassfish-run_hacktest/ to build this pull request and run the TCK using it. I updated the jakarta-concurrency-tck-glassfish-run_hacktest to hack the [Platform TCK GlassFish Concurrency TCK runner suite.xml...

Since I see 17 test failures for `web` instead of 8 failures, I assume I am doing something different and wrong.