No longer need the workaround to disable Validator extensions for JavaFX #539
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
|
Build failed as CI is still on Graal RC10.. let's only merge this after CI is upgraded to RC11 |
Revert "Have Hibernate Validator disable the JavaFX value extractors integration" This reverts commit 68b767fa8e0a951fb6fbe028aa89875424a3a0b3.
stuartwdouglas
force-pushed
the
RemoveJFXWorkaround
branch
from
3c0ee90
to
9f0982e
Compare
|
I have updated the docker image, I have rebased this to test it out. |
|
Looks like this did not trigger CI for some reason |
cescoffier
approved these changes
Jan 19, 2019
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.
Revert "Have Hibernate Validator disable the JavaFX value extractors integration"
This reverts commit 68b767f.