| [jakarta.ee-spec.committee] Jakarta Authorization spec version confusion |
The version of JACC in Java EE 8 is 1.5. Somehow the corresponding API jar file was released as version 1.6: https://mvnrepository.com/artifact/javax.security.jacc/javax.security.jacc-api/1.6 The subsequent jakarta version of the API jar file was released as version 1.6.1: https://mvnrepository.com/artifact/jakarta.security.jacc/jakarta.security.jacc-api/1.6.1 The Jakarta Authorization TCK is for version 1.5 of the spec: http://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8-eftl/staged/eclipse-authorization-tck-1.5.0.zip Sigh. We need to bring all these versions into alignment. The options are: 1. Change the Maven coordinates to jakarta.authorization:jakarta.authorization-api:1.5.0 and keep the spec at version 1.5, and rerun the standalone TCK against the updated API jar file. 2. Bump the spec version to 1.6, update the TCK version to match, and rerun the standalone TCK against GlassFish 5.1. Which do you prefer? P.S. This is not the only case of a version mismatch. We ran into a similar problem with Deployment, where the version should've been 1.2 but was in fact 1.7. We chose option #2 above, which was simpler in this case because there is no standalone Deployment TCK.