|Re: [jakartaee-platform-dev] Java SE 8 or 11 for Jakarta EE 9?|
This is somewhat off topic, but sharing some context here might be useful. In your next reply, could we change the topic to "Jakarta EE Adoption Stories" and move the conversation to the Jakarta EE community alias (hopefully you are part of that alias)?
I have been trying to curate and publicize Java EE adoption stories for a little while. I would like to begin to do the same for Jakarta EE. Any chance you would be willing to be interviewed for that? The interview will look something like this: http://blog.rahmannet.net/2016/08/java-ee-adoption-story-from-pavel.html. I think this helps provide real perspective to people on the fence about adopting Java EE/Jakarta EE.
What do you think?
BTW anyone else willing to share a Jakarta EE adoption story is also most welcome.
Jakarta EE Ambassador, Author, Speaker, Blogger
Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
As a user of the Jakarta EE technologies (yay! we're on Jakarta EE 8,
-------- Original message --------
From: Martijn Dashorst <martijn.dashorst@xxxxxxxxx>
Date: 11/5/19 3:20 AM (GMT-05:00)
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] Java SE 8 or 11 for Jakarta EE 9?
and run fully on Java 11), I wouldn't mind if the Jakarta EE 9 would
require Java 8 as a minimum. As long as it doesn't preclude us from
running our preferred application server on Java 11 and beyond. Should
that make both Java 8 and Java 11 be requirements, we don't mind.
As long as the migration is short, without breaking stuff--other than
the package rename. What happens with Jakarta EE 10 and beyond is
another worthwhile discussion.
Looking forward to learn more about the plans...
On Mon, Nov 4, 2019 at 3:30 AM Kevin Sutter <sutter@xxxxxxxxxx> wrote:
> Since we're trying to nail down the Jakarta EE 9 content before early December, I'm going to start a few separate threads to discuss the major topics.
> Should Jakarta EE 9 keep Java SE 8 as the minimum, or should we move to Java SE 11?
> Note, even if we decide to move to Java SE 11 as the minimum, this does not mean that we will require JPMS. We're only talking about the runtime support. Also, even if we decide to stick with Java SE 8 as the minimum, compatible implementations could support any version of Java SE 8 and beyond.
> Java SE 8 Pros
> Consistent with Java EE 8 and Jakarta EE 8. Limits migration concerns.
> No need to provide the "missing" Java EE technologies that were removed from Java SE 11.
> Still has a long support cycle (2025?).
> Java SE 11 Pros
> Latest and greatest LTS release for Java.
> As you can see, I'm having a tough time justifying the move to Java SE 11 -- especially with all of the required work for Jakarta EE 9, namely the jakarta namespace change.
> Kevin Sutter
> STSM, MicroProfile and Jakarta EE architect
> e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
> phone: tl-553-3620 (office), 507-253-3620 (office)
> LinkedIn: https://www.linkedin.com/in/kevinwsutter
> jakartaee-platform-dev mailing list
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Become a Wicket expert, learn from the best: http://wicketinaction.com
jakartaee-platform-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Back to the top