| Re: [jakartaee-tck-dev] Release of 8.0.2 platform TCK... |
Scott Marlow wrote on 1/9/20 5:55 AM: > Alwin, > > Thanks for bringing up PR#142, I think that there are two commits > associated with PR#142: > > 1. https://github.com/eclipse-ee4j/jakartaee-tck/commit/152b0a6e70f076d4a8c5b8ec84daf9019ca191ff > is directly for PR#142 and updates the now expired client certificate. > I assume the reason to fix is in case the client certificate > expiration date is checked by some implementations. This looks like a case of an impending TCK bug that we don't want to fix by excluding every test that uses these certificates, so we're just going to update these (for testing only) certificates. > 2. https://github.com/eclipse-ee4j/jakartaee-tck/commit/dcf012e6ace5580b10e5df7fc7c018eba92024cd > updates the standalone TCK version for > connector,jacc,jaspic,securityapi,websocket. > > Does anyone object to including these two (non-test) commits in 8.0.2? If the TCK changes, the version number definitely needs to change!