Scott M Stark

I would say yes, but the current TCK process is very anal and says changes can only be made for Java SE version issues. There is an ongoing discussion in...

The EPL is not the correct copyright and license. The referenced handbook entry: https://www.eclipse.org/projects/handbook/#ip-copyright-headers has no requirement to make Eclipse the copyright holder and CDI is Apache licensed. The only...

Maybe one thing that could be done is to create a org.jboss.arquillian.container.test.spi.client.deployment.ApplicationArchiveProcessor that replaces any empty beans.xml with one that has ``. The SPI would simply be to add that...

Links have been updated

This is ready

The tck guide has been updated and a potential challenge has been fixed in a release staged today: https://download.eclipse.org/ee4j/bean-validation/3.1/validation-tck-dist-3.1.0.zip 32d008ee99e28325ef92761891112b7177ad2b6c31881216baa0f3729a8eda03 CCR and results have been updated: https://github.com/jakartaee/validation-spec/issues/281 https://github.com/jakartaredhat/beanvalidation-tck/wiki/Jakarta-Bean-Validation-3.1-TCK-Results

This needs to be marked as a TCK challenge. I'm not able to do this.

I imagine the issue is similar to this java money NBSP discussion: https://github.com/JavaMoney/jsr354-ri/issues/193 Expecting that a locale's formatting is stable over JDK releases seems too fragile to have in the...

Ok, thanks @jhanders34 . In that issue `-Djava.locale.providers=COMPAT` is documented as the workaround. I created a TCK dev issue to document this as needed for passing tests that rely on...

The github repo for the Jakarta RPC project is here: https://github.com/jakartaee/rpc The readme there calls out the spec project page and the mailing list Project page: https://projects.eclipse.org/projects/ee4j.rpc Mailing list: https://accounts.eclipse.org/mailing-list/jakartarpc-dev