Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Maven coordinates for TCK publication
Hi,

>  As per the EFTL license implementations cannot submit compatibility certificate requests (CCR) based on a Maven artifact, they must use a TCK downloaded from the Eclipse downloads webpage.  

If I'm not mistaken, this was labeled as an "urban myth" by Ed Bratt many moons ago. While it holds in principle, if the binary bits are identical, the distinction can not be made and is therefore tolerated. If I'm still not mistaken, Ivar confirmed this to be the practical truth indeed.

There is NO individual SHA posted for any jars that may be present inside a .zip TCK downloaded from the Eclipse downloads site (aka the "big zip), BUT... the uploaders (of the TCK) should ensure that when the big zip is unzipped and contains x.jar, that x.jar downloaded from Maven Central has the same SHA. The vendor can then implicitly use the x.jar downloaded from Maven Central.

Think of it in a different way (it's I think the example Ivar used), if you download the big zip, unpack it, put the jar files in your internal nexus, file server, or whatever, the TCK doesn't suddenly becomes invalid. Maven Central acts as such "internal nexus".

Kind regards,
Arjan Tijms




On Wed, 6 May 2026 at 20:22, Scott Marlow via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:


On Wed, May 6, 2026 at 1:06 PM Mark Thomas via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:
On 06/05/2026 16:37, Scott Marlow via jakartaee-platform-dev wrote:
>  > I ask as, currently, individual projects do not have permission to
> publish to the jakarta.tck group ID.
>
> Which TCK are you asking for just so I understand the context?

Right now, _expression_ Language. But the same applies to Pages, Servlet
and Web Socket.

> Do you mean the Eclipse CI job ssh access level to eclipse downloads? 
> Or actually publishing to Maven Central?  I'm not aware of
> why jakarta.tck on Maven Central would be locked down to certain Eclipse
> projects.

I mean publishing to Maven Central. Currently only the Jakarta TCK
project has permissions to publish to the jakarta.tck group ID.

Thanks for adding the context and others for responding also!

> Now that (most) TCKs have been spun out to individual projects, are
projects required to continue using that group ID or can a project's TCK
be published under the project's own group ID?

I do not recall any requirement that EE TCKs have to be under the jakarta.tck group ID.  Having the TCKs in Maven is only to improve the developer experience (e.g. for potentially debugging TCK tests in an IDE using the published Maven source code artifact).  As per the EFTL license implementations cannot submit compatibility certificate requests (CCR) based on a Maven artifact, they must use a TCK downloaded from the Eclipse downloads webpage.  

Yes, project's TCK can be published under the project's own group ID.

Thanks for opening https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/7308 for the permission problem.

Scott
 

Mark

>
> On Wed, May 6, 2026 at 11:19 AM James Perkins via jakartaee-platform-dev
> <jakartaee-platform-dev@xxxxxxxxxxx <mailto:jakartaee-platform-
> dev@xxxxxxxxxxx>> wrote:
>
>     This was asked on https://www.eclipse.org/lists/jakartaee-tck-dev/
>     msg02189.html <https://www.eclipse.org/lists/jakartaee-tck-dev/
>     msg02189.html> too as an FYI.
>
>     I don't know if there is a hard rule, but I definitely have opinions
>     🙂 I don't think specs should use the jakarta.tck groupId. They
>     should use the jakarta.$spec.tck or something similar. The version
>     the spec uses should be the same as the spec API version too, or at
>     least the major.minor versions need should match.
>
>
> Regarding hard rules, I forget if there is one for the group id.
>
>
>     The problem with using the jakarta.tck groupId is you'd have to
>     version it with the same version is the EE release it would go into.
>     With service releases, we could get into some weird spaces where
>     some specs have a 12.0.0, some have a 12.0.1 and others might have
>     something else for the version.
>
>
> The Persistence 3.2 tests were added to the Jakarta EE 11 Platform tck
> as 3.2 tests via https://github.com/jakartaee/platform-tck/tree/11.0.x/
> tcks/apis/persistence/persistence-outside-container <https://github.com/
> jakartaee/platform-tck/tree/11.0.x/tcks/apis/persistence/persistence-
> outside-container> and we copied these tests to the Persistence spec and
> are maintaining them there.  We didn't copy any EE Persistence tests to
> the Persistence spec though, those will remain in the Platform TCK. 
> There is more to it than I am mentioning which I can elaborate on if
> that would be helpful.
>
> I agree that for EE tests that move to a separate EE spec project it is
> tricky as the versioning needs to be right and probably needs changes to
> the GAV (I think the separate thread that James mentioned is still
> pending to explore this EE Platform TCK -> separate spec TCK topic).
>
> Scott
>
>
>     James R. Perkins
>     Software Developer
>
>     IBM
>     ------------------------------------------------------------------------
>     *From:* jakartaee-platform-dev <jakartaee-platform-dev-
>     bounces@xxxxxxxxxxx <mailto:jakartaee-platform-dev-
>     bounces@xxxxxxxxxxx>> on behalf of Mark Thomas via jakartaee-
>     platform-dev <jakartaee-platform-dev@xxxxxxxxxxx <mailto:jakartaee-
>     platform-dev@xxxxxxxxxxx>>
>     *Sent:* Wednesday, May 6, 2026 08:12
>     *To:* jakartaee-platform-dev@xxxxxxxxxxx <mailto:jakartaee-platform-
>     dev@xxxxxxxxxxx> <jakartaee-platform-dev@xxxxxxxxxxx
>     <mailto:jakartaee-platform-dev@xxxxxxxxxxx>>
>     *Cc:* Mark Thomas <markt@xxxxxxxxxx <mailto:markt@xxxxxxxxxx>>
>     *Subject:* [EXTERNAL] [jakartaee-platform-dev] Maven coordinates for
>     TCK publication
>     All,
>
>     TCKs have previously been published to Maven Central under the
>     jakarta.tck group ID.
>
>     Now that (most) TCKs have been spun out to individual projects, are
>     projects required to continue using that group ID or can a project's
>     TCK
>     be published under the project's own group ID?
>
>     I ask as, currently, individual projects do not have permission to
>     publish to the jakarta.tck group ID.
>
>     Thanks,
>
>     Mark
>
>     _______________________________________________
>     jakartaee-platform-dev mailing list
>     jakartaee-platform-dev@xxxxxxxxxxx <mailto:jakartaee-platform-
>     dev@xxxxxxxxxxx>
>     To unsubscribe from this list, visit https://www.eclipse.org/
>     mailman/listinfo/jakartaee-platform-dev <https://www.eclipse.org/
>     mailman/listinfo/jakartaee-platform-dev>
>     _______________________________________________
>     jakartaee-platform-dev mailing list
>     jakartaee-platform-dev@xxxxxxxxxxx <mailto:jakartaee-platform-
>     dev@xxxxxxxxxxx>
>     To unsubscribe from this list, visit https://www.eclipse.org/
>     mailman/listinfo/jakartaee-platform-dev <https://www.eclipse.org/
>     mailman/listinfo/jakartaee-platform-dev>
>
>
> _______________________________________________
> jakartaee-platform-dev mailing list
> jakartaee-platform-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

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

Back to the top