Re: [jakarta.ee-community] [ee4j-community] Eclipse Jakarta EE TCK commi

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

Stuart Douglas wrote on 04/12/2018 04:27 PM:

On Fri, Apr 13, 2018 at 8:27 AM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

(Resending to new mailing list address.)

Splitting the CTS project so that each individual TCK is relatively independent is a non-trivial (but not impossible) task.  It should definitely be considered, but it would help to have someone lead that effort who is already familiar with the CTS and the JT Harness framework on which it is built.  Does anyone want to volunteer to do that?

Until that is done, updates to the tests for each API will need to be done in the CTS repository.  We'll definitely need contributors from each API project to update the tests as the API evolves.  If you want to help with that, you should start becoming familiar with the JT Harness framework.

If we were going to split the TCK's I think something to be careful of is that different project don't decide to take the infrastructure code in completely different directions. At the moment most of the TCK's use the same infrastructure, and the process for setup and running the tests is pretty much the same.

If this was split into completely independent repositories then it is possible that this would diverge over time, and we could end up with a situation where every TCK has variations and has a slightly different setup/config process.

While a think a split to allow individual JSR's to maintain their own tests could be a good thing, I think that care must be taken to ensure they all continue to use a common infrastructure.

I agree, and that seems like something the PMC should "manage".