Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-tck-dev] Jakarta Core TCK to Central
Hi,

Thanks Ivar, I somehow missed that exact reference, but I remembered it fairly well. Except for the *MUST* to Maven Central. Some work to be done there for the various teams.

Kind regards,
Arjan Tijms



On Wed, 2 Oct 2024 at 10:57, Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi,

This is well documented in the TCK Process: https://jakarta.ee/committees/specification/tckprocess/
In short:

* Projects MUST produce the project licensed (EPL, Apache, etc.) version for distribution to Maven Central or other open source channels, usable for automated, non-official testing, and implementation. No compatibility claims can be made on the basis of this TCK.

* Projects MUST produce a final candidate binary that includes the EFTL license. The Jakarta EE Specification Committee will sign and promote project TCK binary for distribution via Eclipse infrastructure on final approval. This is the TCK binary usable for self-certification when one desires to make a claim of compatibility, allowing for the use of the Jakarta brands.

I hope this clarifies the question.

Ivar

On Wed, Oct 2, 2024 at 9:44 AM Arjan Tijms via jakartaee-tck-dev <jakartaee-tck-dev@xxxxxxxxxxx> wrote:
Hi,

On Tue, 1 Oct 2024 at 13:30, Roberto Cortez via jakartaee-tck-dev <jakartaee-tck-dev@xxxxxxxxxxx> wrote:
If I remember correctly, we do it this way because of the LICENSE, but in MicroProfile, we can publish the TCKs to Central by changing the LICENSE when doing the release.

I remember we actually set some release jobs up to just that; EFTL license for the downloads.eclipse.org publish and EPL for the Maven central publish. One thing to take into account is that for certification you still have to use the downloads.eclipse.org version.

Still, some clarity around this would be appreciated. 
 
Is there any other challenge to not having the Jakarta Core TCK in Central? It is inconvenient to set up as a zip file, and it should work the same way as MicroProfile TCKs.

There was something about the SHA being checked, but not exactly sure what the real technical problem is here.

Kind regards,
Arjan Tijms

 
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev


--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration. 

Back to the top