Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rest-dev] Drop Minimum Java Requirement to Java 17
  • From: Rob McDougall <rob.mcdougall@xxxxxxxxxx>
  • Date: Thu, 14 Dec 2023 15:04:38 +0000
  • Accept-language: en-US, en-CA
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=LjNRBW8RLofctzmvxbF1TyqQl98sMiZncV2PLtP7FZY=; b=IujR8CEyOO2RjgJ1hy5IY/mI80ctXJm5QemLBgqQhqmAuBmRQEH0fFjWujdQhk7jUSL3g/tPIEPnyhYaNA9NXH/z0gO741wlfR/VnLvSRuCrcruuZL0dUxinFvPSxW8DGeIQVI3E/TxIV5ff8aLvAQFpBx1HFXdW66TBTQlWB3N4MRUxuydM72uaeWkyP6ieMNmMm9nXYpYEfDNQa2DaOZecZIhz5Y9Tlzw8+k//lQP8+oHTf12Vsd7+vC18dHCHYk3XDY2J0lAGrgLQkdCB0RaFN/RXY2OqLW8BtrggAuBlWAS4RwqRypq/cvlYKX6LtqVTU+j3dHnWuabqF6V2yA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=VfukYeKpKF6tm6k0EbxchrE2IluafxqOO2x/JuDscLPwNOI+kdQxC4tY8XcfUUwsixZL2lhWXlUcELNB9X11i0Ek82ybDC6nVmvkntQLNnkmoEdzyl9gJJ/80lJljplMyJ2Zol4pCoHlnantBSNsveuOwn0ZTUvcty7m7hLf5LqhowUJoB81S0UxqBRBk4oEbhJSWBwgAMyHdjMKEbgjrSesK60HhrfdbjM7XWXhyQLy5EOm8ZS4lym4jKMTxHlwlu/+kQ+T8OjpjL3ADfgPMNDYWs23adl12U9hiUFGU+SW0+mVXCvWD5epn3J96St+LsAzEOULlJXtgFweNbeemQ==
  • Delivered-to: rest-dev@xxxxxxxxxxx
  • List-archive: <>
  • List-help: <>
  • List-subscribe: <>, <>
  • List-unsubscribe: <>, <>
  • Thread-topic: [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).





Rob McDougall | Senior Technical Architect | 4Point | +1.613.907.6415 |

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

Twitter icon - small  linkedin icon  - small  Facebook icon - small


Upcoming out of office dates:

  Public Holidays: Dec 25th – Jan 1st

  Vacation: Dec 18 th-Dec 20th



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:



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

Back to the top