Re: [DISCUSS] Prepare next Torque release with java 17 baseline

Hi Georg,

also a +1 from me.
The last software I updated from Java 8 was to 17 directly, skipping 11.
Oracle says they dropped "Premier Support" for 11 in 2023 (whatever that 
means exactly)
https://www.oracle.com/de/java/technologies/java-se-support-roadmap.html
According to this we could also target the next LTS version (Java 21) 
for 2026?

Regarding the JDBC compatibility, I don't see any problems. The latest 
JDBC API is Version 4.3 from Java SE 9, which we already skipped.

I would agree on modernisation of the template code (and maybe drop one 
version? sql code is in groovy and velocity)
Also I would like to address some cleanup of the repository. I am more 
of a git user, so when I started to work on the project i was a little 
confused about the folder structure of this project. (e.g. torque4 still 
floating around somehow)

Max

P.S.: i also worked on a gradle-plugin version of the torque-generator, 
which I could provide for implementation for an upcoming version. It is 
currently written in Kotlin and uses a gradle-style project. Rewriting 
it as a maven-project and in Java should be possible, but will need some 
work.


Am 02.09.2024 um 16:52 schrieb Kallidis, Georg:
> Hi Torque Devs,
>
> what about to upgrade Java baseline to version 17 for the next release?
>
> This would be in line with Apache Turbine project v7, which does use Torque as ORM mapper, and is now in the process to upgrade to Java 17.
>
> In my opinion we do not need a vote for this, when discussing is sufficient and no one comes up with an better alternative or other considerations ..
>
> Thanks for your comments!
>
> Best regards, Georg
>
>
>
>
>