[ https://issues.apache.org/jira/browse/AMQ-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895458#comment-17895458 ]
Terje Strand commented on AMQ-9359: ----------------------------------- Wow, that was fast! Thanks and appreciate it! Jetty 11 seems to be going EOL in January 2025 ([https://github.com/jetty/jetty.project/issues/10485)] so its required for us to migrate/upgrade for the use in production. Two questions: - Any specific reason why you chose ee9 rather than ee10 (i.e. servlet version 5 vs 6)? - Anything I could do to help? Would testing with "works for me" help? > 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: 10m > 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: issues-unsubscr...@activemq.apache.org For additional commands, e-mail: issues-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact