Re: [jakarta.ee-spec.committee] Interaction Between Code-First and Speci

[Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx>]

On 2018-05-30 10:40 PM, Bill Shannon wrote:

Mike Milinkovich wrote on 05/30/2018 05:19 PM:

Personally I would recommend sticking to the current plan of putting all of
the TCKs into one project. That at least puts the TCK code into a different
project. The refactoring can happen later naturally. 

I've explained this several times but it doesn't "stick".

A small number of TCKs are already refactored.  Or rather, they were never
integrated with the CTS.  We plan to submit those as separate repositories under
the API projects.

Humorously, I drafted a long-winded response failing to understand this yet again. Good thing I re-read this before hitting send.

It would be good to understand what we want to do in the future if/when the CTS
is refactored.  Where should the refactored TCKs go?  

I think that the end game will be to have individual TCKs, each in their own projects. That is just my opinion, and reasonable people can and will disagree. But the project teams and contributions to the TCKs are different enough from the specifications that I think they need to be different.

We should follow the same
model with the existing TCKs that are already separate.

Well, maybe. But I don't think there is a consensus on the correct approach. And delaying those TCK contributions until that consensus it established seems like a bad idea. Doing a restructuring review and moving these repos into other projects later is a pretty simple process.