gt; > From: "Jochen Theodorou"
> > To: "MG" , "dev"
> > Sent: Monday, December 23, 2024 10:39:55 AM
> > Subject: Re: Replacing javax.* with jakarta.*
>
> > On 21.12.24 16:43, MG wrote:
> >> Hi Jochen,
> >>
> &g
- Original Message -
> From: "Jochen Theodorou"
> To: "MG" , "dev"
> Sent: Monday, December 23, 2024 10:39:55 AM
> Subject: Re: Replacing javax.* with jakarta.*
> On 21.12.24 16:43, MG wrote:
>> Hi Jochen,
>>
>> 1. that
On 21.12.24 16:43, MG wrote:
Hi Jochen,
1. that sounds like a good idea, but I am just wondering if ppl who are
in this situation might not potentially have other (Java) libraries
in use, for which they would need to do the renaming of the class
references also.
In my last project
I think it would be great if someone can document the jakarta
migration via bytecode adjustment process including a Groovy example.
For sure, there will be folks who may not want to follow the typical
javax to jakarta evolution path. If using Groovlets, they would need
to run the tool(s) on the gro
Hi Jochen,
1. that sounds like a good idea, but I am just wondering if ppl who are
in this situation might not potentially have other (Java) libraries
in use, for which they would need to do the renaming of the class
references also.
2. So maybe having a chapter in the Groovy documentati
On 20.12.24 14:24, Paul King wrote:
Well, that would be the idea. Maybe not recommended, but currently you
can still use the 4.0.x groovy-servlet jar with Groovy 5. At least for
Groovy servlets with a simple Jetty server test I just tried.
You certainly wouldn't want both the 4 and 5 groovy-serv
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
> Sent: Thursday, December 19, 2024 4:07 PM
> To: dev@groovy.apache.org
> Sub
-
From: Paul King
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 wrote:
>
> Well, mo
=code&ref=advsearch
> >
> > (The advanced search somehow dropped the "javax" part... 🤷♂️)
> >
> >
> > -----Original Message-
> > From: jost.schwi...@it.nrw.de
> > Sent: Thursday, December 19, 2024 1:59 PM
> > To: dev@groovy.a
King
Sent: Thursday, December 19, 2024 7:38 AM
To: 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 o
ge%3AGroovy+language%3AGroovy+&type=code&ref=advsearch
>
> (The advanced search somehow dropped the "javax" part... 🤷♂️)
>
>
> -Original Message-
> From: jost.schwi...@it.nrw.de
> Sent: Thursday, December 19, 2024 1:59 PM
> To: dev@groovy.apache.org
&g
st.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
*.groovy+language%3AGroovy+language%3AGroovy&type=Code&ref=advsearch&l=Groovy&l=Groovy
-Original Message-
From: Paul King
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 ad
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 y
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 pla
15 matches
Mail list logo
