[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jakartaee-tck-dev] Finalizing the TCKs
|
Just curious -- what is the plan for finalizing the stand-alone
TCKs? I understand there is still some work going on with them --
documentation, maybe exclude lists, etc. But at some point, they
need to be finalized. Certainly once a specification goes to
Ballot, that TCK will need to be frozen -- even if other TCKs from
this project still need work.
Are the build systems set up to start curtailing the production
of TCKs once the APIs go to ballot? Do we have any sense of the
risk that a general problem might be found, as we close out
Jakarta EE 9, that might force all the TCKs to be rebuilt after
some of the ballots conclude?
As a reminder, these stand-alone TCKs are generated in this
project (in wave sequence):
- Wave 0 (Any time)
- Concurrency
- Messaging
- Persistence
- (From the Platform TCK)
- Wave 1 (Any time)
- Annotations
- _expression_ Language
- JSON Processing
- Servlet
- SOAP with Attachments
- WebSocket
- Wave 2 (Planned to start July 28)
- Authentication
- Authorization
- JSON Binding
- Server Pages
- Wave 3 (Planned to start Aug 5)
- Wave 4 (Planned to start Aug 11)
- RESTful Web Services
- Transaction
- Wave 5 (Planned to start Aug 18)
- Connectors
- Standard Tag Library
- (From the Platform TCK)
- Enterprise Beans
- Enterprise Web Services
- Wave 6 (Planned to start Aug 25
- Wave 7 (Planned to start Aug 31)
- Jakarta EE Web Profile
- Jakarta EE Platform
