Re: AW: Question on updating Turbine core

Hi Georg,

Sounds good. I might start by taking a look at the Fulcrum components 
and see if I can help out there.

-

Jeff


On 6/14/24 06:06, Kallidis, Georg wrote:
> Hi Thomas, hi Jeffery
>
> I just started to check an upgrade using jakart.servlet.api 6.1.0 and Java 17 as baseline. With some help tools e.g. from https://github.com/apache/tomcat-jakartaee-migration
> you could quickly start. Yet as Thomas said, there are dependencies to a couple of Fulcrum components.
>
> Additionally Fulcrum Upload has some more migrations:
> - We have to use the new dependency commons-fileupload2-jakarta-servlet6 nevertheless.
> - There is a dependency to Portlet API, should we support this anymore? It might be much easier to drop this.
>
> What do you think?
>
> Best regards, Georg
>   
> -----Ursprüngliche Nachricht-----
> Von: Thomas Vandahl <[email protected]>
> Gesendet: Freitag, 7. Juni 2024 14:51
> An: Turbine Developers List <[email protected]>
> Betreff: Re: Question on updating Turbine core
>
> Hi Jeff,
>
>> Am 05.06.2024 um 20:32 schrieb Jeffery Painter <[email protected]>:
>>
>> Hi Turbine devs,
>>
>> I setup a new Ubuntu 24.0 server the other day for some testing, and realized my apps would not load since by default, they have switched the packages from Tomcat 9.x to Tomcat 10.x. Should we plan to update the Turbine servlet packages to move to the jakarta.* packages instead of javax.servlet ?
>>
> +1 to going for Jakarta. After all, this is where we came from :-)
>
>> I'm not sure what other components might be affected (fulcrum or torque) and also require some updates.
>>
> At least all components which fulfill web tasks (parser, intake, localization?) Torque should not be affected AFAICT.
>
> Bye, Thomas
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>