Hey guys, do we actually need to run the platform-tck?
Markus and myself were looking into it and for example Payara and Wildly are doing standalone setups only: - https://github.com/payara/jakartaee-10-tck-runners - https://github.com/wildfly/wildfly-tck-runners/tree/wildfly-27 So do we actually need the javatest based setup at all(aka platform-tck) ?? Or can we also just do a bunch of standalone tck setups (as we already to in /tck in the TomEE repo) and claim to be compliant if we pass the set needed for the web profile? Hoping for someone, who is more familiar with the certification process (David, maybe??) to jump in to give some guidance? Gruß Richard > Am 23.07.2024 um 12:53 schrieb Jonathan Gallimore > <jonathan.gallim...@gmail.com>: > >> Also I'm far away from doing a complete run, I only ran a couple dozen >> tests so far. Ideally once we figure out these setup issues someone from >> tomitribe could trigger a full run on tck.work so we can get some actual >> numbers. > > I'm happy to help wire that up. > > Jon > > On Tue, Jul 23, 2024 at 11:32 AM Markus Jung <ju...@apache.org> wrote: > >> Hey Richard, >> >> >> I did some initial work on running a few TCK tests in the platform-tck >> the past days and have been able to gain some quick wins with a couple >> of setup issues. [1] >> >> >> This is where I'm at: >> Main pain points are that LegacyCookieProcessor is gone in Tomcat 10.1 >> which causes a bunch of tests to fail and tssv.jar is seemingly missing >> from the platform-tck, which makes the ProviderConfiguration [2] invalid >> as this .jar contains the class >> com.sun.ts.tests.jaspic.tssv.config.TSAuthConfigProvider. Updating the >> Context.xml configs to not reference LegacyCookieProcesor anymore did >> the trick but I'm still trying to figure out what needs to be done to >> get the tssv.jar file. It was in the EE 9.1 TCK but is seemingly missing >> from EE 10. One solution that works is just extracting it from the >> Authentication 3.0 TCK, but I doubt this is the right solution. Maybe >> someone who is more involved knows more? >> >> Also I'm far away from doing a complete run, I only ran a couple dozen >> tests so far. Ideally once we figure out these setup issues someone from >> tomitribe could trigger a full run on tck.work so we can get some actual >> numbers. >> >> Thanks >> Markus >> >> [1] https://github.com/jungm/tomee-tck/tree/ee10work >> [2] >> >> https://github.com/jungm/tomee-tck/blob/main/src/test/tomee-plume/conf/ProviderConfiguration.xml >> >> On 23.07.24 11:06, Richard Zowalla wrote: >>> Hi all, >>> >>> TomEE 10.0.0-M2 is out and it seems, that we have quite a few people >> already testing it, which is great. >>> >>> Since we resolved most of the open dependency updates related to EE10, >> we can now start to work on TCK setup / compliance or at least to get some >> numbers. >>> Aside from the standalone TCKs here [1], we will need to check on how to >> run https://github.com/jakartaee/platform-tck/tree/10.0.x with TomEE 10 >> to (at least) get some numbers. >>> Some of the required tweaks / config options (etc) can be found here: >> https://github.com/apache/tomee-tck >>> >>> I think, that Markus J. did a quick check on the platform-tck, so maybe >> you can add your findings in this thread, so we can (hopefully) create an >> environment for further discussion on how to proceed with the TCK itself. >>> >>> From what I remember on the standalone TCKs: >>> >>> - We need to correctly setup the concurrency TCK and fix our >> implementation if needed. >>> - We need to check on the CDI TCK. >>> >>> All TCKs can be enabled via a specific Maven profile. >>> >>> There are still some other open things: >>> >>> - MP 6.0 requires us to implement OpenTelemetry, which hangs because of >> https://issues.apache.org/jira/browse/OWB-1441 atm. >>> - CXF 4.1.0 needs to be final ;-) >>> >>> So if anyone wants to have a look into one of these areas, feel free to >> drop a message on dev@ >>> >>> Cheers, >>> Richard >>> >>> >>> [1] https://github.com/apache/tomee/tree/main/tck >>
