I was going to do
MaxConcurrency annotation · Issue #136 · eclipse-ee4j/concurrency-api (github.com) and possibly look at
Lock Annotation · Issue #135 · eclipse-ee4j/concurrency-api (github.com)
Steve
From: cu-dev <cu-dev-bounces@xxxxxxxxxxx>
On Behalf Of Nathan Rauh
Sent: 21 October 2021 15:29
To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Subject: Re: [cu-dev] Will there be a staged Jakarta Concurrency 3.0 SPEC API release candidate jar available
Regardless of how the TCK ends up, I would be in favor of publishing a release candidate of the Concurrency spec API jar. This will help Jakarta EE
product providers to better get started experimenting with their implementations, and will give end users a more official copy to experiment with as well, once some of those implementations reach an alpha or beta stage. I think we would want to first confirm
that there aren't any major changes in the pipeline. I don't see any further spec update pulls still out there, but if anyone is still planning additional major contributions to the Concurrency API under Jakarta EE 10, please reply to this discussion so that
we can know to wait for them.
From: "Scott Marlow" <smarlow@xxxxxxxxxx>
To: "cu developer discussions" <cu-dev@xxxxxxxxxxx>
Date: 10/21/2021 08:58 AM
Subject: [EXTERNAL] [cu-dev] Will there be a staged Jakarta Concurrency 3.0 SPEC API release candidate jar
available
Sent by: "cu-dev" <cu-dev-bounces@xxxxxxxxxxx>
[1] has other SPEC API jars that have been made available via some special Eclipse mechanism I believe that is used by other SPEC API projects.
I'm asking since it is not 100% clear if [2] will include the ability to run Jakarta EE Platform container tests in the Concurrency TCK. If the concurrency project could push a release candidate of the Concurrency SPEC API jar
to [1], the platform TCK could start building with that (in case we need the Platform TCK to run a set of Concurrency tests still).
Full disclosure, we need to solve [3] which is about adding (Jakarta EE implementation specific) deployment descriptors to Standalone SPEC TCKs that want to run Platform tests that require specific vendor specific configuration
via deployment descriptors. The existing Concurrent TCK tests that currently have files that are found by search `find -name *sun*.xml` will need a way to deploy such vendor
deployment descriptors.
Scott
[1] https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta
[2] https://github.com/eclipse-ee4j/concurrency-api/issues/145
[3] https://github.com/eclipse-ee4j/jaxrs-api/issues/1039_______________________________________________
cu-dev mailing list
cu-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cu-dev