[
https://issues.apache.org/jira/browse/AMQ-9359?focusedWorklogId=982616&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-982616
]
ASF GitHub Bot logged work on AMQ-9359:
---------------------------------------
Author: ASF GitHub Bot
Created on: 10/Sep/25 13:19
Start Date: 10/Sep/25 13:19
Worklog Time Spent: 10m
Work Description: coheigea commented on PR #1344:
URL: https://github.com/apache/activemq/pull/1344#issuecomment-3274954263
> @coheigea I'm working on converting the Jetty from Spring to use
Jetty-native xml. This will reduce the security risk, by being able to leverage
stock Jetty configurations and allow users to leverage more Jetty features
without having to translate from Jetty bean to Spring bean for configuration.
>
> edited: Latest commit has ActiveMQ booting with Jetty 12 using jetty-based
xml configuration files. The console and api are deploying, but both error out
currently.
@mattrpav What's the most fundamental thing to look at? I was looking at the
distribution, but then I saw the activemq-web-console tests were failing as
well.
Issue Time Tracking
-------------------
Worklog Id: (was: 982616)
Time Spent: 1.5h (was: 1h 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: 1.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
