Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jakarta.ee-spec.committee] Status through wave 4

This is the status as I see it through wave 4. The specs with the ** have version updates required as discussed in the “Other version mismatches beyond JACC” thread? It looks like for Jakarta Concurrency, we will live with the 1.1 version and let the vote go forward?

Jakarta Authorization needs a resolution on the version.  I thought was we wanted to do was use 1.5.0 with
Maven coordinates of 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, but a decision is needed so Arjan and do the update. This is the last
Issue with that PR.

Jakarta XML Registries is still working on TCK

Jakarta Servlet still needs java doc copyright and license in footer corrected. I created a PR against the PR to fix this, but Stuart is saying it is also fixed in main. 

Jakarta RESTful Web Services has few issues related to cert request not being in the right place/type.

The 6 others in blue look good to go for final vote.

Jakarta Annotations
Jakarta Concurrency **
Jakarta _expression_ Language
Jakarta Managed Beans
Jakarta XML Registries
Jakarta Deployment
Jakarta Bean Validation
Jakarta Messaging
Jakarta Persistence
Jakarta JSON Processing
Jakarta Servlet
Jakarta WebSocket
Jakarta Dependency Injection
Jakarta Interceptors
Jakarta Authorization **
Jakarta XML RPC
Jakarta Authentication
Jakarta Mail
Jakarta JSON Binding
Jakarta Server Pages
Jakarta Debugging Support for Other Languages
Jakarta Contexts and Dependency Injection
Jakarta Batch
Jakarta RESTful Web Services
Jakarta Transactions



Back to the top