-
Notifications
You must be signed in to change notification settings - Fork 29
Upgrade gaffer-tools to build with Java 8 and Java 11 #850
Comments
Edited ticket to remove modularisation from the scope. |
The work required for the Java 11 upgrade has been drafted in the gh-850-java11 branch. Not many changes were required beyond removing use of deprecated functionality that is removed in Gaffer v2. There is a problem with the |
The changes in Gaffer itself and in #995 are sufficient for Gaffer Tools to build with Java 11. |
It was decided that the POM for Gaffer Tools should have a Java 11 profile to automatically create Java 11 code when a Suitable version of the JDK is used - the same as exists in Gaffer. This should be straightforward to do and will be done as part of the next release. |
In fact, we don't need to add a Java 11 profile. The profile from Gaffer which enables Java 11 is inherited though the Gaffer POM and is now automatically used in Gaffer Tools. No further work is therefore required to add a profile to Gaffer Tools. This profile has been tested and Gaffer Tools is working correctly with Java 11. This issue can now be closed. |
This issue has been retroactively added to the alpha 2 release notes as it is a new feature that was enabled by upgrading tools to work with alpha 2. |
This issue has been rescoped to add a feature not in #995
@GCHQDeveloper314 said: "It was decided that the POM for Gaffer Tools should have a Java 11 profile to automatically create Java 11 code when a Suitable version of the JDK is used - the same as exists in Gaffer. This should be straightforward to do and will be done as part of the next release."
The text was updated successfully, but these errors were encountered: