[tomcat] branch master updated: Complete javax -> jakarta rename.

This is an automated email from the ASF dual-hosted git repository. markt pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/master by this push: new f5efdad Complete javax -> jakarta ren

Re: javax -> jakarta rename

There are imo 3 ways we can deal with the migration. All of them assume that all of our ASF projects migrate the affected packages from javax.* to jakarta.*. A.) of course have all the customer code and libs migrated to jakarta.*. B.) ClassTransformer + ClassLoader. The ClassTransformer

Re: javax -> jakarta rename

I see a lot of value to the runtime solution cause it is the only one enabling an ops only migration so for all the softwares in "run only" phase it is the only option. However the agent or transformer is the least invasive solution cause it does not require to patch core libs and will avoid app

Re: javax -> jakarta rename

On 12/21/2019 11:49 AM, Mark Thomas wrote: On 21/12/2019 17:45, Adam Rauch wrote: Yes, I see that 9.x javax.* will be supported for a long time and I'm all in favor of killing off deprecated EE libraries. I want to encourage our users to migrate to Tomcat 10.x and future releases as

Re: javax -> jakarta rename

On 21/12/2019 17:45, Adam Rauch wrote: > Yes, I see that 9.x javax.* will be supported for a long time and I'm > all in favor of killing off deprecated EE libraries. I want to encourage > our users to migrate to Tomcat 10.x and future releases as quickly as > possible, but I'm concerned that

Re: javax -> jakarta rename

On 12/21/2019 3:11 AM, Rémy Maucherat wrote: On Sat, Dec 21, 2019 at 7:36 AM Adam Rauch > wrote: I've watched with great interest the recent list discussions surrounding javax -> jakarta renaming and the draft release numbering plan. I'm curious: Would

Re: javax -> jakarta rename

On Sat, Dec 21, 2019 at 7:36 AM Adam Rauch wrote: > I've watched with great interest the recent list discussions surrounding > javax -> jakarta renaming and the draft release numbering plan. I'm > curious: Would the Tomcat team consider making a Tomcat release that > supports BOTH the javax and

Re: javax -> jakarta rename

Hi Adam, Did you evaluate a class transformer added to tomcat classloader? This can stay quite light and enables the same while not using app loader - standard tomcat mode. For app loader case integrations can do the work easily (spring and friends) since they all have asm or equivalent. Hope it

javax -> jakarta rename

I've watched with great interest the recent list discussions surrounding javax -> jakarta renaming and the draft release numbering plan. I'm curious: Would the Tomcat team consider making a Tomcat release that supports BOTH the javax and jakarta package names? Please hear me out before