[
https://issues.apache.org/jira/browse/AMQ-9359?focusedWorklogId=950423&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-950423
]
ASF GitHub Bot logged work on AMQ-9359:
---------------------------------------
Author: ASF GitHub Bot
Created on: 29/Dec/24 15:09
Start Date: 29/Dec/24 15:09
Worklog Time Spent: 10m
Work Description: mattrpav commented on PR #1344:
URL: https://github.com/apache/activemq/pull/1344#issuecomment-2564753319
> So we can probably stick with EE9 until 7.x. I guess if someone wants to
use EE10 and with an embedded version of AMQ they could probably still do so as
long as they were not using anything that relied on the EE9 stuff (any of the
AMQ websockets or servlets, etc) and they would have to exclude the EE9
transitive dependencies from AMQ
If users embed, they *should* be able to do EE10 runtime by excluding
activemq-http and activemq-web-* modules. I _believe_ the other EE specs in use
are forward compatible b/w EE9 and EE10.
Issue Time Tracking
-------------------
Worklog Id: (was: 950423)
Time Spent: 1h (was: 50m)
> 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: 1h
> 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
