Status update:
- We're down to our last 7 failures on the general portion of the EE 9.1 TCK.
Jean-Louis and I are on it.
- 3 jaxrs
- 1 servlet
- 1 securityapi
- 2 websocket
- We have the signature tests to configure and run still and there will be
failures there, but they should be easy to correct. Jon is currently looking
at this.- Jakarta CDI and @Inject standalone TCKs are all in good shape as those are setup and run against the CDI 3.0.0 TCK in OpenWebBeans - Jakarta Debugging Support for Other Languages 2.0 TCK is passing. Thanks, Cesar! - Jakarta XML Binding 3.0 TCK results will be obtained from the Eclipse JAXB implementation. - Jakarta Bean Validation 3.0.0 TCK results against Apache BVal needs considerable more work and won't be ready for tomorrow. Jon spent a good 26 hours on it and could get many tests passing, but there appear to be issues with the bytecode transformation. As such TomEE 9 Plume has been momentarily switched to Hibernate Validator which is Apache License v2 and safe to ship. We'll use that to certify so we have time invest in getting Apache BVal to be Jakarta Bean Validation 3.0 compliant and can switch Plume back to Apache BVal. If all the above can land in the next 24 hours, we'll be able to start the release process at this same time tomorrow and not just be certified for the first time since Java EE 6, but be included in the Jakarta EE 9.1 release itself! If we can make this happen, it will be the biggest milestone this project has crossed since the Java EE 6 Web Profile certification of TomEE 1.0.0-M1 in October, 2011. On a related note, Jean-Louis and myself are also responsible for conducting the actual Jakarta EE 9.1 release ballot over on the Eclipse side. Needless to say, it's a historic moment for the project and we should all be so incredibly proud. Let's make this happen! We can do this! -David
smime.p7s
Description: S/MIME cryptographic signature
