Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] TCK tests in the same repo as API and Spec
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

Haven't we had this discussion before somewhere? Just can't find where we documented it...

Ivar

On Thu, Jan 30, 2020 at 7:46 PM Andy Guibert <andy.guibert@xxxxxxxxx> wrote:
Hi all,

Currently all of the Jakarta EE TCK tests are housed in one big repo and they use a custom test framework from the Java EE days:

 It is more convenient to have the TCK tests in the same repo as the API and spec docs because as the technologies change over time all 3 parts (tck/api/spec) can be updated in the same PR. Additionally, implementations can then consume the TCK tests as Maven artifacts and run/verify that they pass the TCK. This is what MicroProfile has done and it works very well.

As an example, I've started this off with the JSON-B TCK test here:

Just wanted to share this with the wider dev community and encourage other specs to follow suit as time permits.

Cheers, Andy
-- IBM
_______________________________________________
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


--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation, Inc.

Eclipse Foundation: The Platform for Open Innovation and Collaboration

Back to the top