Re: [jaspic-dev] Vendor Implementation TCK Expectations

[arjan tijms <arjan.tijms@xxxxxxxxx>]

Hi,

The old-tck-runner and subsequently the old tck itself currently has to be configured and run as the vendor did previously (for EE 9).  There's a service release coming up anyway that will build and run the old TCK like is done for Security now: https://github.com/jakartaee/security/tree/master/tck/old-tck

That would probably also be a good opportunity to add profiles in a way that works well for WildFly and others.

Thoughts?

Kind regards,

Arjan Tijms

On Wed, Jun 15, 2022 at 11:38 AM Darran Lofthouse <darran.lofthouse@xxxxxxxxx> wrote:

Can I just double check the expectations for the complete Authentication TCK for Jakarta EE 10.

From our previous discussions we have a strategy for the new tests to dynamically add a profile to the root pom to target whatever VI is under test.

Is it also a requirement to run all of "old-tck-runner" against the VI?  Looking at the pom for this one it doesn't seem profile based and seems to assume GlassFish only unless I am miss-reading the pom.

--

Darran Lofthouse

Red Hat

darran.lofthouse@xxxxxxxxx   

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