| Re: [jakartaee-platform-dev] Maven coordinates for TCK publication |
|
This was asked on
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.
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.
James R. Perkins
Software Developer
IBM
From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> on behalf of Mark Thomas via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx>
Sent: Wednesday, May 6, 2026 08:12 To: jakartaee-platform-dev@xxxxxxxxxxx <jakartaee-platform-dev@xxxxxxxxxxx> Cc: Mark Thomas <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 To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev |