The Spec. committee was unable to reach any conclusion regarding
publication of Final specification TCKs to a public Maven
repository, though there was speculation that there are
specifications that may do this already. I am not aware of any
requirement, nor even any desirability for publishing any TCK that
is not proposed final with a TCK license. Furthermore, the hash
tracking that the specification process provides has no facility
for ensuring that the archive has been obtained from one location
or another so if a final TCK were obtained from maven central,
that TCK would pass via all the HASH checks (There may be a
process requirement about download location and that is one of the
things that needs further research by the Spec. committee).
Additionally, any pre-final TCK release that is promoted to final
(i.e. CI build, Milestone build, whatever, promoted without
rebuilding) will pass the HASH sum checks. Unfortunately, the
process we are under (at least as outlined here) recommend that
only a Proposed Final TCK include the EFTL and this will almost
certainly require the archive be rebuilt on anything published
earlier than a proposed final release.
I realize this may force rerunning tests that have been performed
on pre-final releases but, until we are able to work out
additional details of the process and license, we cannot make
other recommendations.
CI, Milestone Release TCK -- any TCK build that is published for
early access and testing