Robert Lichtenberger

I am also affected by this problem.

Having upgraded to gradle 7.3, this problem still occurs, forcing us to import our project with gradle 6.6.1, which in turn prevents us from using any nice features in gradle....

FWIW we have solved this problem ultimately by using the testFixtures plugin which forced us to separate real test code from test infrastructure code. Unfortunately using the testFixtures plugin not...

Thank you, @james-bryant for the workaround. WIth this is I can import the project into eclipse. Unfortunately Issue #1035 then kicks in...

Is there any chance of this happening on the main branch so that JavaFX Library projects will be able (without any hassle) to add the plugin?

Any news on this issue? As the maintainer of ValidatorFX I am not able to release a "correct" POM-File of the library at the moment :-(.

For what it's worth: I (the OP) have since used a subclass of Scene as a workaround that will install an event filter on key events, an check each keypress...

Since warning/error-messages must be translatable (i18n), these messages must always be provided by the client of ValidatorFX. Here are things that I would consider common checks: - Field is required...

Considering the following piece of code: ``` validator.createCheck() .dependsOn("usePatientId", usePatientId.selectedProperty()) .dependsOn("useName", useName.selectedProperty()) .dependsOn("exactBirthDate", exactBirthDate.selectedProperty()) .dependsOn("theFirst", theFirst.selectedProperty()) .withMethod(c -> { if (!(boolean) c.get("usePatientId") && !(boolean) c.get("useName") && !(boolean) c.get("exactBirthDate") && !(boolean)...

Turns out this is not as simple as removing the JavaFX Plugin from `build.gradle`, we also require another version of ControlsFX.