Re: [jakarta.ee-spec] Another possible CDI issue

[Emily Jiang <emijiang6@xxxxxxxxxxxxxx>]

Since you are doing Milestone release, it is perfectly fine to do a TCK 3.0-M3 instead of 3.0.3. Am I missing something? I also think it does not require a vote.

Thanks

Emily

On Tue, Sep 8, 2020 at 2:10 PM Scott Stark <starksm64@xxxxxxxxx> wrote:

That is correct, there are no spec or api changes. It was simply that the process of removing the JWS related tests from the TCK was incomplete. There is a 3.0.2 staging of the TCK that has fixed the issues that could replace the current 3.0.1 staged version on the ballot PR.

On Tue, Sep 8, 2020 at 8:06 AM Kevin Sutter <sutter@xxxxxxxxxx> wrote:

I had talked with Scott Marlow briefly about this before he posted his question to the mailing list...  

My initial thought was that this could be resolved by a patch update to the TCK.  I didn't see where this would require a change to the Spec or the API.  To me, a simple update to the 3.0.x version of the TCK would suffice.  Am I being too optimistic?

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter

_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec

--

Thanks
Emily