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

["Kevin Sutter" <sutter@xxxxxxxxxx>]

Ivar,
We did discuss
this and documented it in the Operations Guide:
https://github.com/jakartaee/specification-committee/blob/master/operations.adoc#recommended-specification-project-repository-structure

Recommendation
was to have one repo for the Spec and API, and a separate repo for the
TCK.  So, they can be in the same Project, but the TCK should be in
a separate repo.

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:
       Ivar
Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>
To:
       jakartaee-platform
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date:
       01/30/2020
13:31
Subject:
       [EXTERNAL]
Re: [jakartaee-platform-dev] TCK tests in the same repo as API and  
     Spec
Sent
by:        jakartaee-platform-dev-bounces@xxxxxxxxxxx

---

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:
https://github.com/eclipse-ee4j/jakartaee-tck 

 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:
jsonb-api pr: https://github.com/eclipse-ee4j/jsonb-api/pull/221
yasson (impl) pr: https://github.com/eclipse-ee4j/yasson/pull/379

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_______________________________________________
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