| Hi Ed
Minor clarification below
Hi Scott, We'd be grateful for assistance. I will let Bhat, Ankit and
others chime in about where you and/or other community members can
best contribute. Once all the third party components are approved
by the Eclipse EMO, we can start moving the Jenkins work forward.
There are other components which will have to be adjusted as the
platform moves to higher Java SE versions. No doubt this will be
part of the Jakarta EE evolution work.
Summary of the plan
We expect to create Jenkins build jobs, similar to what we have
done with the other TCKs. JAXB TCK, since it is not included in
the uber jakartaee-tck project will have separate build jobs that
are included with Jenkins for "Eclipse Project for JAXB" (here) and we intend
to add another sub-job to the general "stand-alone" TCK aggregator
in the jakartaee-tck Jenkins jobs (e.g. jakartaeetck-nightly-run).
This will be similar to what we do with the JavaMail TCK. This
might not be done right away since this isn't a required element
of Java EE 8.
At this point, with respect to Java EE 8, and probably Jakarta EE
8, the JAXB TCK testing won't be strictly necessary (but Jakarta
EE 8 isn't
written yet so this is not a certainty). Almost certainly it will
be required by subsequent Jakarta specifications when the platform
moves to higher versions of the runtime, where JAXB is no longer
available by default. (In case anyone reading this is curious:
JAXB is deprecated in Java 9 and 10 and eliminated in 11. Google
found this
article, by Jesper de Jong, which includes a nice
explanation of what's happened and what to do for general Java
applications.)
For Java EE 8 and below, if an app server is not using the JAXB provided by Java SE and is including an implementation, the running of the JAXB TCK is required to validate the implementation is compliant.
If an app server does not include JAXB, then yes the running of the JAXB TCK is not required.
We look forward to Jakarta EE specifications that will provide
the requirements for addressing changes necessitated by the
evolution of Java SE runtime.
-- Ed
On 3/15/2019 9:03 AM, Padmanabha Bhat
wrote:
Hi
Scott,
We have done only the initial contribution of the source files
for JAX-B TCK. The CQs are being filed for libraries and will be
included in the repository after the approval. We will start
building the standalone TCK once the contribution is complete.
Thanks,
--Bhat
On 3/15/2019 9:07 PM, Scott Marlow wrote:
Hi,
I'm not currently setup to locally build the jaxb-tck [1] but am
curious as to what the next steps are for getting that build as
part of the standalonetck-nightly-build-run [2]?
Are there parts that others can help with?
Scott
[1] https://github.com/eclipse-ee4j/jaxb-tck
[2]
https://jenkins.eclipse.org/jakartaee-tck/job/standalonetck-nightly-build-run
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
_______________________________________________ jakartaee-tck-dev mailing list jakartaee-tck-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037Oracle Java Engineering 1 Network Drive Burlington, MA 01803Lance.Andersen@xxxxxxxxxx
|
