One thing to note, there is a tool that scans your classes and makes the necessary changes in the bytecode. We have used this to deploy a Tomcat 9 (Java EE 8) war onto Tomcat 10 (Jakarta EE 9).
https://github.com/apache/tomcat-jakartaee-migration ________________________________ From: Paul King <pa...@asert.com.au> Sent: Thursday, December 19, 2024 7:38 AM To: dev@groovy.apache.org <dev@groovy.apache.org> Subject: [EXT] Re: Replacing javax.* with jakarta.* External Email: Use caution with links and attachments. Well, most of those files are false positives. The "JavaSE" (JDK) still has many javax packages whereas only JavaEE classes are affected. As far as I can see, there's the handful of classes we know about in groovy-servlet and some related test files and a related build file. There's also some javax.inject references in our build files, but that is a separate tooling issue and doesn't affect any visible artifacts that we produce. We also have some javax.annotation annotations usage for some rarely used files, but they are essentially a tooling/documentation thing - not so much related to the JavaEE change. But I agree we should look at those before Groovy 5 is released. Cheers, Paul. On Thu, Dec 19, 2024 at 11:06 PM <jost.schwi...@it.nrw.de> wrote: > > Sorry, "only" 133 files: > https://urldefense.com/v3/__https://github.com/search?q=javax*repo*3Aapache*2Fgroovy*path*3A*.groovy*language*3AGroovy*language*3AGroovy*&type=code&ref=advsearch__;KyUlKyUqKyUrJSs!!GFN0sa3rsbfR8OLyAw!ZN5ve1EUuMQL_dzwslNdL43BTjQ2BniErfsWJvw7uDkr04Lk2RA_rzuPXTR7Xo38C8hihWCAgcXg-TWVqXKpWw$ > > (The advanced search somehow dropped the "javax" part... 🤷♂️) > > > -----Original Message----- > From: jost.schwi...@it.nrw.de <jost.schwi...@it.nrw.de> > Sent: Thursday, December 19, 2024 1:59 PM > To: dev@groovy.apache.org > Subject: RE: Replacing javax.* with jakarta.* > > Thanx for your fast response! > > We have 5 projects using groovy-servlet - and Tomcat 9 support will end > 2025... > > I know that e.g. groovy-xml is also using javax. > > OMG, a quick code search in the groovy repository finds over 2400 files: > https://urldefense.com/v3/__https://github.com/search?q=repo*3Aapache*2Fgroovy*path*3A*.groovy*language*3AGroovy*language*3AGroovy&type=Code&ref=advsearch&l=Groovy&l=Groovy__;JSUrJSorJSsl!!GFN0sa3rsbfR8OLyAw!ZN5ve1EUuMQL_dzwslNdL43BTjQ2BniErfsWJvw7uDkr04Lk2RA_rzuPXTR7Xo38C8hihWCAgcXg-TVHCBqsnw$ > > > -----Original Message----- > From: Paul King <pa...@asert.com.au> > Sent: Thursday, December 19, 2024 12:02 PM > To: dev@groovy.apache.org > Subject: Re: Replacing javax.* with jakarta.* > > Thanks for the prompt Jost. I just added a comment in the issue. > TL;DR, yes we should do that. Help welcome as we haven't had any folks > volunteer to do that yet. > > Note, there are other projects like Micronaut, Grails, etc. that have already > advanced moving forward with Jakarta changes. > Also, when you say many subprojects, what did you have in mind over and above > groovy-servlet? > > Cheers, Paul. > > On Thu, Dec 19, 2024 at 6:40 PM <jost.schwi...@it.nrw.de> wrote: > > > > Regarding to > > https://urldefense.com/v3/__https://issues.apache.org/jira/browse/GROOVY-11190__;!!GFN0sa3rsbfR8OLyAw!ZN5ve1EUuMQL_dzwslNdL43BTjQ2BniErfsWJvw7uDkr04Lk2RA_rzuPXTR7Xo38C8hihWCAgcXg-TVVscraWg$ > > > > All "javax.*" libs have to be renamed to "jakarta.*" - e.g. when switching > > Tomcat from 9 to 10 (Jakarta EE 9). > > (Special "thanx" to SUN for this "service"! 🙄) > > > > There are many Groovy subprojects using javax.* ... 🤷♂️ > > Are there any plans to adapt Groovy accordingly? > > > > Thanx in advance! > > Jost
