Java 17 upgrade #369
Merged
Java 17 upgrade #369
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
carter-cundiff
approved these changes
Sep 26, 2024
|
Q: Will we need to upgrade the CI jobs to use jdk 17? |
ewilkins-csi
force-pushed
the
feature-java17
branch
3 times, most recently
from
6a8160c
to
90f451e
Compare
- pull scala version up to build-parent - fix relative parent path warning - remove unused imports - remove unused inf recursion - fix package path - fix string utils import - rename smallrye graphql version property - move logging dependencies up to root so they can be used in build-support - add more Apache commons to root - remove unused incremental build profile - remove unused fields/imports - add plugin version to cucumberin build-support - de-duplicate fabric8 conf in spark-infrastructure - remove pom/bom import from dependencies in invocation-service - fix templates (bom removal and groupId fix) - simplify pipeline CDI with composition
#355 upgrade core library to support jdk17
[#354] Modified PDP to build with Java 17
356 Update mavenUtils to be compatable with jdk17 356 Create aissemble compatible quarkus bom 356 Create migration to update spark configs with version update
#356 Spark working with java17
#356 Correct foundation core pyproject imports
ewilkins-csi
force-pushed
the
feature-java17
branch
from
90f451e
to
0033e33
Compare
Disable `metadata` as it is failing, and bump the Java installation in the build/release actions to 17.
Addressed in the latest commit |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that 1.9 has been cut and dev is on 1.10 we can merge in the Java upgrade branch. This will allow us to work directly off of dev instead of managing a feature branch.