First concurrency is going to do a service release to address challenges on Full Profile, essentially disabling the tests. This will be 3.0.1.
For the Web Profile issue I think the team needs spec committee guidance on what to do. We can either allow Web Profile implementations to use an exclusion list to exclude the relevant test suites,
which is a big chunk of the tests, as some of the tests suites are deployed as EAR files. Alternatively we restructure the tests with specific profiles as there are aspects that need to be tested in Full Profile which are not possible in Web profile e.g. application.xml
support.
Steve
From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Ondro Mihályi
Sent: 01 July 2022 14:15
To: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
Cc: jakartaee-tck developer discussions <jakartaee-tck-dev@xxxxxxxxxxx>; jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] [glassfish-dev] PR for Jakarta EE 10 results
So all passes now except for Concurrency on Web Profile, right? Concurrency is about to create a new release, they just need to sort out whether it will be just a patch release or a minor release (which requires
a new ballot).
Ondro Mihalyi
Director, Jakarta EE expert
Omnifish OÜ, Narva mnt 5, 10117 Tallinn, Estonia | VAT: EE102487932
|
