I've begun working on the Jakarta 10 migration. I tried with a 4.x branch [1], but it's difficult to maintain with the number of commits in the main branch. So I decided to switch to a different mechanism. I've created several branches upstream : * jakarta-rewrite [2] : contains a migration shell script [3] to be executed regularly (I'll try to setup a github action at some point in the near future). This scripts uses perl regular expressions and git to perform most of the upgrade. When executed, the script will first rebase on top of the main branch, run the migration and force push to the jakarta-rewritten branch * jakarta-rewritten [4] : contains the migrated code. The idea is to have it regularly and automatically updated and run to have an idea of the current state. It's not yet buildable ! * jarkarta-jetty [5] : contains one commit [6] to be merged as part of the migration executed by the script [7]. Other branches may be set up as needed. Those are used for things that can't be done with simple shell commands.
I'll keep you posted ! Cheers, Guillaume [1] https://github.com/apache/camel/pull/8579 [2] https://github.com/apache/camel/tree/jakarta-rewrite [3] https://github.com/apache/camel/blob/jakarta-rewrite/jakarta/transform.sh [4] https://github.com/apache/camel/tree/jakarta-rewritten [5] https://github.com/apache/camel/tree/jakarta-jetty [6] https://github.com/apache/camel/commit/e5aea792291557b86b10eb84b978b381c2d94be6 [7] https://github.com/apache/camel/blob/8c60590d18542665e5048780f674d499f900c604/jakarta/transform.sh#L224 ------------------------ Guillaume Nodet
