AW: Question on updating Turbine core

Hi Jeff,

Turbine parent 12 sets Java 11 and Turbine Core v6.0 does use this version. 
Nevertheless we could test and support building with newer java versions, I still would expect no problem until at least Java 21.

I am currently in the process to update Turbine 13 (currently still SNAPSHOT) setting Java version to 17 and to update Fulcrums and Turbine core along this version with Jakarta and Servlet 6.1. I think, I got Turbine running with the following Fulcrum components updated (mostly due to Jakarta):

Intake
localization
parser
security/api
pool
upload

For Fulcrum-upload I have to check, if it is indeed not used anymore and could be replaced as Thomas said by Fulcrum-parser or Commons-Upload. I already did some updates though.

If nobody complains I'll check this into the trunk/main branches.

Of course testing the new baseline with turbine-parent 13-SNAPSHOT will set the lower limit to Java 17.

Best regards, Georg

-----Ursprüngliche Nachricht-----
Von: Jeffery Painter <[email protected]> 
Gesendet: Freitag, 14. Juni 2024 15:37
An: [email protected]
Betreff: Re: Question on updating Turbine core


I'm pretty sure these are the minimum fulcrum components needed to run Turbine 6.0 based apps:

cache
crypto
factory
intake
json-api
json-jackson2
localization
mimetype
parser
pool
security-api
security-memory
security-torque
testcontainer
xslt
yaafi

So I can start investigating these, and also make sure they are all building with jdk-11+

-

Jeff



On 6/14/24 09:32, Thomas Vandahl wrote:
> Hi Georg,
>
>> Am 14.06.2024 um 12:06 schrieb Kallidis, Georg <[email protected]>:
>>
>> 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.
> My understanding is that Fulcrum-Upload is no longer necessary. I implemented Parts handling in Fulcrum-Parser long ago.
>
> 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]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]