[
https://issues.apache.org/jira/browse/GUACAMOLE-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17834746#comment-17834746
]
Nick Couchman commented on GUACAMOLE-1325:
------------------------------------------
This may be what is required to get things to run under Tomcat 10.x; however,
to fully achieve the swap to Jakarta EE there are quite a few classes that need
the javax.* items migrated to their jakarta.* counterparts.
[~z0rb]: I'm sure there will be a point at which we freeze the feature set, but
I'm not sure that will be immediate - I think we probably want to get the 1.6.0
version released, first, before we make such a freeze - depending on how long
that takes we can decide if we want to freeze it. Also, with the strategy we
have with our branches - patch, main, and next - we should be able to commit
changes like the Jakarta transition and Angular migration into the next branch,
while still working on other items - patches or features - in main. Obviously
the more changes we make the harder it will be to keep up the required
migration, so I think a freeze will make sense at some point.
> Apache Tomcat 10.0 Servlet API incompatibility
> ----------------------------------------------
>
> Key: GUACAMOLE-1325
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1325
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole, guacamole-common, guacamole-ext
> Affects Versions: 1.3.0, 1.4.0
> Reporter: Mathias
> Priority: Major
>
> Guacamole client 1.3.0 is not working with Apache Tomcat 10. Apache Tomcat
> 10.0.x requires a new Servlet 5.0 API. The Java package has changed from
> javax.servlet to jakarta.servlet.
> [Migrating from Tomcat 9.0 to 10.0|http://tomcat.apache.org/migration-10.html]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
