Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] [cu-dev] Service release approach has been approved

Thanks Scott.


I think it would be also good to test against Open Liberty as Open Liberty was used to bring the api to ballot originally.




From: cu-dev <cu-dev-bounces@xxxxxxxxxxx> On Behalf Of Scott Marlow
Sent: 28 July 2022 10:21
To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Cc: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [cu-dev] [jakartaee-platform-dev] Service release approach has been approved



On Thu, Jul 28, 2022, 4:56 AM Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:

That’s great news.


Just for my own knowledge who is leading the refactoring work?

That was done by Scott Stark via which is marked as merged.


I think the next step is to release the 3.0.2 TCK to and for that to be tested with GlassFish (Web Profile + Full Platform).







From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Scott Stark
Sent: 27 July 2022 17:22
To: cu developer discussions <cu-dev@xxxxxxxxxxx>; jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: [jakartaee-platform-dev] Service release approach has been approved


The Specification Committee has approved an exception to the TCK process to be able to change tests in a service release for the current issue to resolve that inability of the TCK to run in the Web Profile.

cu-dev mailing list
To unsubscribe from this list, visit

Back to the top