[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-tck-dev] How to build the Platform TCK to target JDK8 but support running with JDK11?
|
On 6/30/20 3:39 PM, Kevin Sutter wrote:
Scott,
Now we have two threads going on this topic... :-) That's okay, I'll
try to keep up...
Kevin,
I actually just renamed the subject in the original thread but not all
email clients will use the original thread. :-)
Thanks Kevin for the reminder that we have many in the community that
will view this as a new thread. We should avoid renaming email subjects
for this reason. My apologies to all of you.
Question: Does Glassfish plan to be compliant with Java 8?
The last I
heard, they were only looking to be compliant with Java 11. If
Glassfish is not interested in Java 8, how are we going to determine
whether the TCK is executable and testable with Java 8?
Excellent question!
We did say that it is optional to also test with Java 8, which I suppose
is true for all implementations, including GlassFish 6.0.
The "how" we are going to determine if the TCK is executable and
testable with Java 8 will be very hard without having an implementation
that can be run on Java 8.
Since the Java
8 compliance is optional, is this additional testing and verification
required before we can claim Jakarta EE 9 is complete?
Good question, under the current release plan, IMO, we should plan to
deliver TCKs that can be passed on Java 8.
Or, do we wait
until a vendor tries the Java 8 compliance testing and then work through
the problems?
I think that we need more input on deferring working through the
problems to the first implementation that tries running the TCKs on Java
8.
This might get messy if we have to modify some tests
after we go final with Java 11...
Yes, IMO it would be too messy to expect a server implementation to work
out the Java 8 compliance testing on their own.
I don't have all the answers. Just
questions to think about and figure out before we claim Jakarta EE 9 is
done...
The good news is that we are here discussing this in the open on this
mailing list, so that we can gather more input.
Thanks for raising this topic!
And thanks for asking these follow up questions! :-)
Scott
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From: Scott Marlow <smarlow@xxxxxxxxxx>
To: Alwin Joseph <alwin.joseph@xxxxxxxxxx>, jakartaee-tck developer
discussions <jakartaee-tck-dev@xxxxxxxxxxx>
Date: 06/30/2020 14:30
Subject: [EXTERNAL] Re: [jakartaee-tck-dev] How to build the Platform
TCK to target JDK8 but support running with JDK11?
Sent by: jakartaee-tck-dev-bounces@xxxxxxxxxxx
------------------------------------------------------------------------
Hi Alwin,
Thanks for raising these points! :-)
On 6/30/20 1:52 PM, Alwin Joseph wrote:
Hi Scott,
Can you please help confirm or correct me on the below 2 statements.
1. The final TCK bundle should be built with JDK11 only. We will not
build the platform TCK using JDK8.
We should target generating JDK8 classes, so that compatible
implementations may also run with JDK8.
From
https://eclipse-ee4j.github.io/jakartaee-platform/jakartaee9/JakartaEE9ReleasePlan
states:
"
Java SE Version
For inclusion in Jakarta EE 9, specification’s APIs MUST be compiled at
the Java SE 8 source level. However, compatible implementations of the
Jakarta EE 9 Web Profile and Full Profile MUST certify compatibility on
Java SE 11. Compatible Implementations MAY additionally certify and
support Java SE 8.
"
Excellent point to raise, the hard requirement is that our build
generates JDK8 classes, although we could also generate separate JDK8 +
JDK11 TCK bundles.
IMO, we could stick with building with JDK8, which is less work than
switching to building with JDK11. I will update the $subject to reflect
this point. :)
2. The final TCK bundle should be used to run tests on both JDK8 & JDK11.
We must run/pass the final TCK bundle on JDK11, as per above linked
JakartaEE9ReleasePlan.
Since we expect that EE 9 compatible implementations could also run on
JDK 8, I think that we should also run against JDK8 ourselves (so that
we know that its possible). IMO, we should next focus on passing
completely with JDK11, so that we finish that first. Then, we should
also pass completely with JDK8.
Thoughts?
Scott
Regards,
Alwin
On 30/06/20 8:14 pm, Scott Marlow wrote:
It would be good to get started on building with JDK11, however, we do
need to target JDK8 so that the EE 9 TCKs also can run on JDK 8 as well.
Has anyone tried building the Platform TCK against JDK 11 yet? The
same question for the Standalone TCKs?
Issue #213 [1] is the general issue for JDK 11 support (Alwin already
installed JDK 11 via JDK11_HOME=/opt/jdk-11.0.7) + issue#145 [2] is a
related issue.
I'm trying to build the Platform TCK locally with JDK 11 using [3], I
have some additional local changes that I will push later and also
share what I see.
Scott
[1] https://github.com/eclipse-ee4j/jakartaee-tck/issues/213
[2] https://github.com/eclipse-ee4j/jakartaee-tck/issues/145
[3] https://github.com/scottmarlow/jakartaee-tck/tree/jdk11
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visithttps://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
