[
https://issues.apache.org/jira/browse/GUACAMOLE-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810912#comment-17810912
]
Irmin Okic commented on GUACAMOLE-1325:
---------------------------------------
I'm aware of it not necessarily getting picked up once the priority gets
raised. I was thinking it may raise the visibility, if someone is picking up a
task, might raise the chances of it getting seen. Also since Spring is the
defacto standard, not being able to get security patches should warrant a
higher priority.
Currently I am also not able to fork this and give it a go because of time
constraints. Similar with the volunteers no doubt ...
Upgrading only guacamole-common would probably not be possible, since it is not
a separate project. Looks like all or nothing.
>From the README: "Each project contained here is completely independent of
>guacamole-client and can be built separately, though the others may have to be
>built first. If all projects are built using guacamole-client, Maven will take
>care of the proper build order." Can be built, but probably not worked on
>separately. :-/
> 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: Minor
>
> 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)
