Re: [jakartaee-platform-dev] TCK tests in the same repo as API and Spec

[Andy Guibert <andy.guibert@xxxxxxxxx>]

Thanks Mike, that actually helps my case =)

For Ivar's other reason:

> 1. The TCK will most likely have a different release cycle because of challenges and such

The TCK could still technically have its own release cycle if we want. But one thing that MicroProfile does that I quite like is that API/Spec/TCK all have the same release cycle so they stay in sync nicely.

In any case, I hope that the benefits I outlined in the OP outweigh your concerns Ivar. For example with Yasson/JSON-B, we like to run the TCK test as part of our CI/CD pipeline so we know with every code change that we are still in compliance with the spec. Previously we had to clone all of Glassfish in our pipeline just to drive some JSON-B tests that could easily be executed in a JavaSE environment and JUnit. Now it's greatly simplified and I can run the JSON-B TCK tests for Yasson with a simple `mvn test` command in under 20 seconds.

On Thu, Jan 30, 2020 at 1:56 PM Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx> wrote:


> I am not sure it is such a good idea to have the TCK in the same repo as the spec doc and api.
> At least two reasons come to mind:
>
> 1. The TCK will most likely have a different release cycle because of challenges and such
> 2. The TCK has a different license

Apologies for being pedantic, but to be clear the final TCK *binaries* have a different license. The source code uses the same open source license as the other artifacts for the specification (either ALv2 or EPL+GPL-CE).
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev