The following specifications, marked in the TCK column as "??" do
not have an API specific TCK
Thank you very much Ed! I was spinning around in circles trying to figure out where they were.
Can someone expand please the criteria used to make the TCK column Done or In Progress?
I made it under Reza's suggestion. I did it quickly last night therefore is not the best tracker possible. We could add other symbols if you prefer.
My idea was to distinguish between
done : completed or ready for creating the package
in progress : there are already some pull requests -- see the comments -- or someone said he is working on it
missing : there is no one taking care of it ( yesterday I tried my best to look at comments in the issues and the past pull requests, but maybe I missed someone)
Web Profile TCK is the Platform TCK, but run with different
command-line properties. The details should be described in the
Web Profile TCK users guide. I don't know if there needs to be a
separate tracking issue (from the Platform TCK) for this. I'm not
actually sure if I see a tracking issue for either full or
web-profile TCKs. Regardless, I think that ought to be filed
against the Jakarta EE Platform API project.
Debugging support TCK is generated from debugging-support-for-other-languages-tck.
There are tracking issues, but they aren't progressing. The
implementation is the Server Platform (GlassFish, in EE4J, for
example). It is pretty general so I don't know if too much work
will actually be necessary. We do need to track it though.
XML Binding TCK is generated from this repo: jaxb-tck .
There is certainly activity in all the related repositories: JAXB
API, TCK, and Implementation. Perhaps we are missing a tracking
issue for this one? (I didn't see one.) I think that all the
related API delivery issues are supposed to be filed against the
API repository (jaxb-api)
then it's up to the Dev. team to manage, however they see fit.
The following specifications, marked in the TCK column as "??" do
not have an API specific TCK:
Enterprise Beans
Enterprise Web Services (Formerly JSR 109)
Interceptors
Compatibility for these APIs (as well as the others which do not
have separate TCKs: Managed Beans and Web Services Metadata) is
verified by either running the complete Platform TCK, or running
the Platform TCK and specifying the appropriate command-line
properties.
Hope this helps,
-- Ed
On 5/28/2020 6:20 PM, Ed Bratt wrote:
The spreadsheet attachment indicates difficulty in determining
status of many of the TCKs.
I believe that the TCK
nightly download folder will contain the results of
nightly TCK builds -- this folder includes stand-alone TCKs
built from the JakartaEE-TCK project by the "standalonetck-nightly-build-run-master"
Jenkins job and contains a mixture of Jakarta EE 8 and 9 TCKs at
this point (though they are all "nightly build" quality. The
organization of this folder may change so probably you'd want to
watch the jakartaee-tck GitHub project and/or the corresponding
-dev e-mail list to stay up to date on this.
I believe that the TCK committer team is getting more and more
of the build-production issues resolved. As of a couple of days
ago, I think all [1] these TCKs are being built (give a
shout-out to the TCK committer team for this accomplishment). I
don't think we are very far on the verification spectrum with
these TCKs, but producing them all is certainly an excellent
accomplishment.
The part of the job that generates the results is still failing
so that isn't updated in the last completed run but there is
another one in progress. Maybe there will be updated results
soon.
-- Ed
[1] This is the list of TCK .zip files created by the most
recently completed Jenkins build job (from the Jenkins job
console output) Each of these has a corresponding info.txt file
which contains the SHA256, size, version and date of the
associated .zip (These each have wildly different quality status
levels at this point so please don't presume these are
functional without checking with the corresponding API project
team):
Thanks Theo for putting this
together. I'll loop in the Jakarta EE Community alias so
hopefully the right folks can help get to the right status.
There have been a few folks waiting to figure out where to
contribute.
In particular, I would like to
understand what the next steps for JSTL is. The project is
currently very Oracle heavy and Oracle committers do not
seem to be available at the moment. There might be other
projects in a similar situation but I am not sure.
Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as an individual
community member and do not reflect the views of my
employer.
On 5/28/2020 7:41 PM, Theodor
Augustin Dumitrescu wrote:
Hi folks,
I created this report for keeping an overall status of
the projects. I'm having some issue tacking the TCK
situation for every project. So feel free to update it.