Sorry, "only" 133 files: https://github.com/search?q=javax+repo%3Aapache%2Fgroovy+path%3A*.groovy+language%3AGroovy+language%3AGroovy+&type=code&ref=advsearch
(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://github.com/search?q=repo%3Aapache%2Fgroovy+path%3A*.groovy+language%3AGroovy+language%3AGroovy&type=Code&ref=advsearch&l=Groovy&l=Groovy -----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://issues.apache.org/jira/browse/GROOVY-11190 > > 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
