-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JavaFX plugin forces Gradle to put libraries on the modulepath instead of the classpath #94
Comments
I believe this plugin no longer needs to depend on the modularity plugin, which appears to be the cause of this issue (as of Gradle 6.4). |
As workaround, remove javafx-gradle-plugin and add JavaFX manually:
This works with Gradle 6.7. All used JavaFX modules must be added because transitiv dependencies are not solved automatically. For my use case, the javafx-gradle-plugin should only resolve transitive dependencies of JavaFX module and platform. |
Thanks.
|
Hi @mrcjkb , Would you be interested in creating a PR for the plugin to remove its dependency on the modularity plugin when used with Gradle 6.4 and later. |
Sure. I'll look into it when I have some time. |
How to reproduce:
Given a modular project with a module-info.java in its main root.
And the following Gradle config:
And a non-modular test dependency, e.g.
testImplementation("com.tngtech.archunit:archunit-junit5:0.14.1")
And a test case, e.g.
When I run the test case with Gradle 6.7.1
Expected behaviour: Then the test case runs
Current behaviour: Then the test case does not run, due to a
java.lang.module.ResolutionException
The text was updated successfully, but these errors were encountered: