Re: Starting to move Gump to using Java 11

On 10/08/2021 21:17, Adam Jack wrote:
> Thanks for the update. Good luck.

Thanks. I think I am going to need it. This is going to be *far* from 
simple.

There is lots of code currently being built by Gump that needs changes 
to build with Java 9+.

You will have seen I started to try and hack around the issues with 
Commons Lang 2.4 (it was using source=1.4) but forcing source to 1.6 
(the minimum Java 11 supports) just creates a different problem - the 
source using "enum" as an identifier but it is a reserved word from Java 
5 onwards.

I don't see a simple or quick solution for this.

Is there a way in Gump to get just some projects to build with a 
different JAVA_HOME? Switching just the Tomcat 10.1.x builds to Java 11 
is the minimum requirement. We can then take a harder look at the 
dependency chains and see what we can do to update versions / trim 
things down.

Mark



> 
> Adam
> 
> On Tue, Aug 10, 2021, 15:57 Mark Thomas <[email protected]> wrote:
> 
>> All,
>>
>> Since Tomcat's main development branch now requires Java 11, I have
>> started the process of moving Gump over to Java 11.
>>
>> So far, I have added Java 11 to the packages installed by Puppet.
>>
>> I want to confirm that Java 11 has been installed, then I'll switch
>> JAVA_HOME to point to Java 11 rather than Java 8. In theory that should
>> 'just work'. When it doesn't (optimistic soul that I am), we'll have to
>> see what fails and figure out the best way to deal with each issue.
>>
>> Once everything is running smoothly on Java 11, then I'll remove Java 8.
>>
>> Mark
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>