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

[Richard Monson-Haefel <rmonson@xxxxxxxxxxxxx>]

Although some of the TCKs have been refactored I think they should all go under the same TCK project at first and then broken out into sub-projects later according to the commenters wishes on the TCK project. Let them figure out what makes the most sense after having wrestled with the code base for a while.  This streamlines the process of getting the TCKs into the repo while keeping it separate from the specification in terms of the process of managing committers. 

On Wed, May 30, 2018 at 9:40 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> 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.

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?  We should follow the same
model with the existing TCKs that are already separate.

_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee