Scott M Stark

@arjantijms Can you validate the latest Concurrency TCK with https://github.com/jakartaee/concurrency/pull/264 ?

The current CCRs are already out of date, so this can be merged: ``` current: shasum -a 256 /tmp/jakarta-jakartaeetck-10.0.0.zip cfe4db9cf5f2bf5cfff568377f7a799c3dc4624e882585a0c659d781764183dd /tmp/jakarta-jakartaeetck-10.0.0.zip current CCR sha256: 62a9cbbf46315ef4b5487fdbdf6e628d272fa3ace9148c5716ba57ea4415df19 ```

There are 1.7.0.Alpha* release artifacts that were used by TCKs for the EE 9 testing. Arquillian is slow to produce final releases, so I would look to use the current...

@dependabot recreate

@arjantijms Is there a requirement in terms of what the unit test class is doing? I looked at some threads the TCK list but did not see this issue mentioned.

I fixed the ee10 ref to ee9 in the 3_0 facelettaglibrary, but I don't understand the point of the jakartaee-schemas when it has only ever contained a fraction of the...

@ivargrimstad This should be merged based on the spec committee meeting today.

This is already supported via the deploymentExportPath property of the arquillian.xml engine configuration or by setting the arquillian.deploymentExportPath system property. See the "Export the Deployment" section of this guide: https://arquillian.org/guides/getting_started_rinse_and_repeat/#export_the_deployment...

Ah, ok, I misread the code. Maybe an importPath property on @Deployment along with an importer utility class would suffice.

From https://jakarta.ee/specifications/platform/10/jakarta-platform-spec-10.0.html#java-platform-module-system-jpms > 13.3. Java Platform Module System (JPMS) > The EE10 release introduced a requirement for every component specification API jar included a JPMS module-info.class suitable for use with...