[
https://issues.apache.org/jira/browse/AMQ-9359?focusedWorklogId=946867&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-946867
]
ASF GitHub Bot logged work on AMQ-9359:
---------------------------------------
Author: ASF GitHub Bot
Created on: 05/Dec/24 13:58
Start Date: 05/Dec/24 13:58
Worklog Time Spent: 10m
Work Description: cshannon commented on PR #1344:
URL: https://github.com/apache/activemq/pull/1344#issuecomment-2520401523
Is there any reason not to bump to Java EE 10? Jetty 12.x can run multiple
EE versions simultaneously so there's not really a reason to not just go to
Servlet 6.0 and Jakarta EE 10 that I can think of. A user that depends on
embedded Jetty and AMQ wants to use EE9 for other servlets could still include
those jars and be compatible.
Issue Time Tracking
-------------------
Worklog Id: (was: 946867)
Time Spent: 0.5h (was: 20m)
> Upgrade to jakarta.servlet-api 6.0.0 & Jetty 12.0.x
> ---------------------------------------------------
>
> Key: AMQ-9359
> URL: https://issues.apache.org/jira/browse/AMQ-9359
> Project: ActiveMQ Classic
> Issue Type: Dependency upgrade
> Reporter: Jean-Baptiste Onofré
> Assignee: Matt Pavlovich
> Priority: Major
> Fix For: 6.3.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> FYI, we don't have any Karaf release supporting jakarta.servlet-api and Jetty
> 11 for now.
> Regarding the timing, we can directly jump to servlet-api 6.x and Jetty 12.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
