Re: [rest-dev] Drop Minimum Java Requirement to Java 17

[Rob McDougall <rob.mcdougall@xxxxxxxxxx>]

• Once Spring is willing to contribute to Jakarta REST they are welcome to share their opinion in this discussion forum. Until today we did not receive any contribution from Spring.

 

So only contributors get a say, not users?  I think you’re forgetting who you’re developing the spec for… 😊

 

Regards,

Rob

 

Rob McDougall | Senior Technical Architect | 4Point | +1.613.907.6415 | www.4Point.com

Receive our news and announcements before anyone else - follow us on:

    

 

Upcoming out of office dates:

  Public Holidays: Dec 25^th – Jan 1^st

  Vacation: Dec 18 ^th-Dec 20^th

 

 

From: Markus Karg <markus@xxxxxxxxxxxxxxx>
Sent: Thursday, December 14, 2023 11:18 AM
To: 'Jakarta Rest project developer discussions' <rest-dev@xxxxxxxxxxx>
Cc: Rob McDougall <rob.mcdougall@xxxxxxxxxx>
Subject: AW: [rest-dev] Drop Minimum Java Requirement to Java 17

 

Once Spring is willing to contribute to Jakarta REST they are welcome to share their opinion in this discussion forum. Until today we did not receive any contribution from Spring.

-Markus

 

 

Von: rest-dev [mailto:rest-dev-bounces@xxxxxxxxxxx] Im Auftrag von Rob McDougall via rest-dev
Gesendet: Donnerstag, 14. Dezember 2023 16:05
An: Jakarta Rest project developer discussions
Cc: Rob McDougall
Betreff: Re: [rest-dev] Drop Minimum Java Requirement to Java 17

 

Has anyone discussed this with the maintainers of spring-boot-jersey-starter? 

 

Spring has committed to supporting Java 17 throughout the Spring Boot 3.x lifecycle.  This may be an impediment for them to adopt Jakarta REST 4.0 or they may be able to work around it.  They may allow you to bring in 4.0 if you’re using Java 21 or they may stick with 3.1.

 

Personally, I use that for many projects.  I would be disappointed if I was stuck on 3.1 even if I was using Java 21 (due to lack of support for Java 17).

 

Regards,

Rob

 

Rob McDougall | Senior Technical Architect | 4Point | +1.613.907.6415 | www.4Point.com

Receive our news and announcements before anyone else - follow us on:

    

 

Upcoming out of office dates:

  Public Holidays: Dec 25^th – Jan 1^st

  Vacation: Dec 18 ^th-Dec 20^th

 

 

From: rest-dev <rest-dev-bounces@xxxxxxxxxxx> On Behalf Of James Perkins via rest-dev
Sent: Thursday, December 14, 2023 9:49 AM
To: Arjan Tijms <arjan.tijms@xxxxxxxxxxx>
Cc: James Perkins <jperkins@xxxxxxxxxx>; Jakarta Rest project developer discussions <rest-dev@xxxxxxxxxxx>
Subject: Re: [rest-dev] Drop Minimum Java Requirement to Java 17

 

You don't often get email from rest-dev@xxxxxxxxxxx. Learn why this is important

 

 

On Wed, Dec 13, 2023 at 3:12 PM Arjan Tijms <arjan.tijms@xxxxxxxxxxx> wrote:

Hi,

 

On Wed, 13 Dec 2023 at 18:03, James Perkins <jperkins@xxxxxxxxxx> wrote:

To me it comes down to the question of adoption. Do we want people to adopt the new Jakarta REST 4.0 specification? If yes, running on Java SE 17 seems like we would get the most adoption.

 

It's similar to discussions that we had since about Java 1.2 really. Back then it was staying on Java 1.0 vs adopting Java 1.2, and not even that long ago in Java EE 8 staying on Java 6 vs Java 8.

 

Eventually, was it ever an issue?

 

For some customers, it definitely was.

 

 

I mean, JDK 21 was released, instead of putting more time into JDK 17. Why did the Java SE team even release 21, if putting more time and energy into Java 17 updates would mean larger adoption of Java?

 

Or would pushing the ecosystem forward eventually mean more adoption?

 

That's impossible to say. Looking in the past though, corporations and government agencies are slow to adopt new things. Does that mean they may be slow to adopt Jakarta REST 4.0? Probably, but the least barrier of entry the better. Again, only Jakarta REST and Jakarta Concurrency are the only two individual specs moving beyond Java SE 17. 

 

 

Kind regards,

Arjan Tijms

 

 

 

--

James R. Perkins

JBoss by Red Hat