[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakartaee-platform-dev] JDK 8 support for Jakarta EE 9
|
Can I play devil's
advocate? In the past, Java EE and Jakarta EE would specify a *minimum*
level of Java SE that it was requiring. Java EE 8 and Jakarta EE
8 specified Java SE 8 as the minimum. But, several application servers
also support newer versions of Java SE -- 9, 10, 11, etc. These application
servers didn't necessarily come out and state that they were Java EE 8
or Jakarta EE 8 compatible with Java 11 (for example). But, the application
server documents support for Java 11. I'm not aware that anybody
called "foul" on that and I am by no means advocating for it.So, if you buy
into that argument, then why wouldn't the reverse also be okay? Somebody
declares they are compliant with Jakarta EE 9 using the required Java SE
11. But, the application server also supports Java SE 8. As
long as they don't advertise they are compliant using Java SE 8, then there
should be no "foul". End users may end up using Jakarta
EE 9 with Java SE 8, but without a formal compliance statement. If
an application server wants to be put on the Compliance page with Java
SE 8 as the runtime and advertise their compliance with Java SE 8, then
the formal certification would be required.
---------------------------------------------------
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/kevinwsutterFrom:
Bill
Shannon <bill.shannon@xxxxxxxxxx>To:
jakartaee-platform
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>, Scott
Stark <starksm64@xxxxxxxxx>Date:
01/29/2020
13:18Subject:
[EXTERNAL]
Re: [jakartaee-platform-dev] JDK 8 support for Jakarta EE 9Sent
by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
Yes.
Scott Stark wrote on 1/29/20 9:52 AM:There may not be one unique runtime approach,
but the question is, if a vendor claims JDK8 support, do they have to pass
the TCK running a Java 8 SE? On Wed, Jan 29, 2020 at 10:40 AM Tibor
Digana <tibordigana@xxxxxxxxxx>
wrote:Nop. That's not the only one dev process.
Today the devs use local JDK8 and devops use JDK11. There is no one unique
process you may think of.Dňa st 29. 1. 2020, 16:09 Scott Stark
<starksm64@xxxxxxxxx>
napísal(a):If a user is expecting a EE release to
support Java SE 8 that is what they will be using for the runtime.The TCK
has to pass while running with Java SE 8 I would say. On Wed, Jan 29, 2020 at 4:48 AM Tibor
Digana <tibordigana@xxxxxxxxxx>
wrote:In my understanding the compiler version
should be 1.8+ but the runtime JRE should be 11+ due to the reliability
of the container.Dňa ut 28. 1. 2020, 16:57 Kevin Sutter
<sutter@xxxxxxxxxx>
napísal(a):Hmmm...
We stated that Compatible Impls MUST support Java SE 11, but they MAY also
support Java SE 8. Isn't that very similar to stating that Compatible
Impls MUST support EJBs, but they MAY also support BMP and CMP Beans?
I was assuming that the Java SE 8 optional requirement would be part of
the Platform spec. Especially since we also indicated that the APIs
need to be compiled at the Java SE 8 level.
If we're saying that the Compatible Implementation doesn't have to support
the optional pieces, then that will need to be discussed and resolved at
the Spec Committee.
If this is just a TCK requirement, then what would we state in the Platform
Spec?
This is an especially pertinent discussion now that the support for Java
SE 8 has been extended to 2030...
---------------------------------------------------
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: "Steve
Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>
To: jakartaee-platform
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date: 01/28/2020
04:09
Subject: [EXTERNAL]
Re: [jakartaee-platform-dev] JDK 8 support for Jakarta EE 9
Sent by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
I agree I'm not sure whether the release plan meant it to be a formally
a spec item.
-----Original Message-----
From: jakartaee-platform-dev-bounces@xxxxxxxxxxx<jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Bill Shannon
Sent: 28 January 2020 02:07
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: [jakartaee-platform-dev] JDK 8 support for Jakarta EE 9
I believe we agreed that JDK 8 support is optional for Jakarta EE 9.
I believe we also agreed that one of the Compatible Implementations submitted
with the specification approval MUST support all optional features.
I think this means that GlassFish is required to support JDK 8 and JDK
11.
Or is some other project planning to be the first Compatible Implementation?
I don't have a problem with allowing others to support JDK 8 and JDK 11
if they want to, but I fear it's going to be a fair amount of work for
GlassFish, and requires a commitment from every component that contributes
to GlassFish.
I'm wondering if we can instead handle this as some sort of TCK compatibility
rule instead of including it in the spec?
That's not as clean, but it would remove the spec requirement and thus
allow GlassFish to support only JDK 11 if that's what it wants to do.
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev