| Re: [jakarta.ee-spec.committee] Still have the final TCK link chicken/egg problem |
One possibility is to simply refer download links in embedded
documents (i.e. User Guides, Readme, etc.) to the appropriate
Jakarta EE specification page (e.g. for Annotations
2.0). That page will be updated once the spec. is ready for
ballot so it will be correct, once everything has been set. I have
been recommending that the user guides use the name patterns as
they currently are being generated from JakartaEETCK builds (see here).
Each is <specification-name>-tck-x.y.z.zip (where x.y.z is
the Spec. version number) in their included documentation.
Projects outside of JakartaEETCK might not follow the same file naming conventions, but those projects do know the name of their final TCK.zip file and the Jakarta EE specification page, will ultimately include a link to the TCK.
It's an extra click, but may help reduce the number of things that need last minute updates.
In the Compatibility Certification Request issue and TCK results summary page, I would recommend the full path URL be used. That needs to reference/confirm the final TCK file anyway since the SHA256 must be quoted as well. We know the transformation rule between the staged and final URL so it shouldn't present too much of a problem to make that last change.
Staged Annotation 2.0 TCK is:
https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee9-eftl/staged-900/jakarta-annotations-tck-2.0.0.zip
(this may vary depending on the project)
Final Annotations 2.0 TCK will be:
https://download.eclipse.org/jakartaee/annotations/2.0/jakarta-annotations-tck-2.0.0.zip
(this pattern should be consistent across all specifications).
Yes, this could be simplified but I think it works. Any comments?
-- Ed
In the review checklist we are asking for the Link to final TCK download zip file of the form https://download.eclipse.org/jakartaee/{spec}/x.y/*{spec}-tck-x.y.z.zip in both the index.md and certification requests. These links do not exist prior to the spec review being finalized and someone from the specification committee promoting the final TCK from the https://download.eclipse.org/ee4j project download area.
We had this issue during the Jakarta EE 8 reviews and it was a problem we talked about addressing.
As an example, the JAF spec PR and certification request show this issue where the TCK links do not exist:
This is the link in the requests:
It actually exists at:
For the spec PR and initial CI certification request, we should just be referring to the project download TCK and it should be a requirement for whoever promotes the approved TCK to update the project _index.md. The initial certification request should just be referring to the project download version.
_______________________________________________ jakarta.ee-spec.committee mailing list jakarta.ee-spec.committee@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee