GUACAMOLE-1325: Migrate from javax to jakarta namespace.#972
GUACAMOLE-1325: Migrate from javax to jakarta namespace.#972necouchman wants to merge 2 commits intoapache:nextfrom
Conversation
Well, turns out Tomcat 10 requires Java 11, so that's settled. |
|
Hi! Thanks a lot for starting this! I've been trying to find time to try it out. |
|
@z0rb The code has not been merged, so there will be no artifacts or builds with this change, yet. Yes, you will need to clone/patch locally and build yourself to test it out. |
|
Looks good on Java 17 and Spring-Boot 3.2.5! Thanks again! Hope this makes it into main once the open questions @necouchman mentioned are resolved. |
Thank you for testing! It will not go into |
|
Thanks for the Tomcat10 patch, I've deployed it and the only issue I have is with the OpenID Connect extension that throw this error :
Mind you, I've only used guacamole-history-recording-storage / guacamole-auth-sso-openid / guacamole-auth-totp / guacamole-auth-jdbc. |
|
I've deployed the Guacamole 1.6.0 from "next" branch as well, but my Tomcat 10 fails to start the guacamole.war. |
This is fully expected:
|
|
I read your initial statement ... But anyway, I guess I misinterpreted the red "Closed" labels as "Merged" labels, a few posts above. My bad. |
Yes, I was referring to the code from this pull request, not from the
That was simply Github letting you know that someone else has mentioned this PR in a request that has been closed. The overall status of this pull request is still |
|
Hello, I've arrived here as a result of trying to install Guacamole unaware of the Tomcat 10.x incompatibility. I see the pull request aiming to fix this is a few hundred commits behind? Normally I wouldn't mind, but I am wondering if this would be a potential security issue if I wanted to compile it myself, or if there's anything I should be aware of before deploying it for personal use. Thank you! |
Yes - this is very much a draft, and a lot of changes were made for the 1.6.0 version that is underway. This will likely not make it into a Guacamole version prior to 2.0.0 because of the incompatible nature of the changes being made (once we merge this, Guacamole will not work with Tomcat versions prior to 10.x). I wouldn't suggest deploying this in any production or public context. |
|
@necouchman Thanks for the update, what is your estimate when this PR will be merged? Or 2.0.0 will be released? |
There is no time-frame for that release. We're still trying to get 1.6.0 out the door. There will likely be a 1.7.0 feature release in there, and 2.0.0 will involve some fairly significant changes, like this and migration from AngularJS to Angular for the front-end. |
|
FYI I have managed to quick and dirty merge 1.6.0 into this branch and it seems to work well. |
|
Thanks, @z0rb. At some point, soon, I'll try to get this re-based on the current |
|
For reference, Fedora 43 migrated from Tomcat 9 to 10 (https://fedoraproject.org/wiki/Changes/Tomcat10ChangeProposal). I submitted a bug report to Fedora, which references this pull request (https://bugzilla.redhat.com/show_bug.cgi?id=2428278). The work around is to downgrade to the Fedora 42 Tomcat packages, but I thought it was worth noting this change here. |
|
Hello, all, I have re-based this against the current |
|
I have tested your branch jira/1325 with Tomcat 10.1.52 and it works. |
Okay, well, here we go. This PR takes care of the migration from the
javax.*namespaces to the newjakarta.*counterparts, updates dependencies, and updates the licenses. I've got it all in a single commit, now, because I couldn't find very clean places to break up the commit - dependency management at this level reminds me of the cat-in-bathtub gif.The code does compile, I'm able to install it into Tomcat 10.1, and run it, log in (JDBC), and start Guacamole session. It's worth noting that this will be a big change in terms of compatibility:
doc/licensesdirectory. I suspect I've left a lot of unused cruft around in getting things updated.I'm going to put this in Draft mode for now - I welcome comments, requests for changes, and testing.