Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jakartaee-spec-project-leads] Publishing TCK results; TCK location; TCK documentation review

I wanted to summarize a few discussions that have occurred recently.
There's some important details here; sorry this message is so long.

- Publishing TCK results

TCK results need to be published in a permanent, stable location for
each release of a Compatible Implementation.  TCK results should *not*
be included as content in the jakarta.ee/specifications Pull Request.

TCK results should be published in some location related to the project,
e.g., on the project's web site, on the project's wiki, or in the
project's repository.  It's up to the project where to publish them.
For example, I've published the results for Jakarta Mail here:
https://eclipse-ee4j.github.io/javamail/TCK-Results.html

TCK results need only include the summary/total lines from the JavaTest
output (as in the example above).  The complete list of which tests have
been passed is not required, but may be included.


- TCK location

The staged version of the EFTL-licensed TCK for a project should be
published in the project's download area on download.eclipse.org.
Currently most of the TCKs are created in the jakartaee-tck project.
The staged versions of these TCKs are available here:
https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee8-eftl/staged/?d
The URL of the staged TCK zip file should be included in the
jakarta.ee/specifications Pull Request.

For projects produced outside of the jakartaee-tck project, we recommend
a directory structure under download.eclipse.org of the following form:

<project>/tck/eftl/	- staged EFTL-license versions of the TCK
<project>/tck/epl/	- EPL licensed non-final versions of the TCK

This is only a recommendation; projects are free to organize their download
directory however they want.

After approval, the TCKs will be signed and published at this location:
https://download.eclipse.org/jakartaee/<project>/<major>.<minor>/<zip-file-name>
where <project> is the project's short name from the "Code" column of
this spreadsheet:
https://docs.google.com/spreadsheets/d/18SraPxRBCOyaS6w-UV6TR-UA1bWy1--sV0ky6msAjWY/edit#gid=0
This download location should appear in the _index.md file of the
jakarta.ee/specifications Pull Request.


- TCK documentation review

We strongly encourage all Project Leads to review the documentation,
and especially the TCK User's Guide, included with the TCK zip files.
Any problems with the documentation should be corrected via Pull Requests
to the appropriate TCK project (e.g., jakartaee-tck), or via issues filed.


Back to the top