feat: upgrade dependencies to use Java 17 and jakarta #139
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
|
As a heavy user of the validator, we embed the jar as a dependency. As the infrastructure partly runs on a java 11 stack, these code changes would make it impossible to ship it the current way. It would be great to have multiple target runtimes with that switch the jakarta/javax dependencies and different target java versions instead of replacing the current one. |
|
Are you using Version 1.5.0 normaly? |
|
Sorry, I was totally confused by all the components of eforms. We are not using it, no issue with that! |
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.
I upgraded some Dependencies to be able to build and run this Application with Java 17 and Jakarta Classes.