Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jakarta.ee-spec.committee] Still have the final TCK link chicken/egg problem

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:

https://github.com/jakartaee/specifications/pull/172
https://github.com/eclipse-ee4j/jaf/issues/40

This is the link in the requests:
https://download.eclipse.org/jakartaee/activation/2.0/jakarta-activation-tck-2.0.0.zip

It actually exists at:
https://download.eclipse.org/ee4j/jaf/tck/eftl/jakarta-activation-tck-2.0.0.zip

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.

Back to the top