Thanx a lot!

BTW: Am I right in thinking that we are introducing a hard cut?
That is: GroovyServlet, TemplateServlet, etc. in Groovy 5 only run on Tomcat 
version 10 (and higher) - and in Groovy 4 only on Tomcat version 9 (and lower).

Just for my understanding...


-----Original Message-----
From: Paul King <pa...@asert.com.au> 
Sent: Thursday, December 19, 2024 4:07 PM
To: dev@groovy.apache.org
Subject: Re: Replacing javax.* with jakarta.*

Here's a PR that does what I think we need to do:

https://github.com/apache/groovy/pull/2136


On Thu, Dec 19, 2024 at 11:38 PM Paul King <pa...@asert.com.au> wrote:
>
> 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://github.com/search?q=javax+repo%3Aapache%2Fgroovy+path%3A*.gr
> > oovy+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+l
> > anguage%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

Reply via email to