-
Notifications
You must be signed in to change notification settings - Fork 59
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
Support using JavaFX jars from gradle classpath or defined directory #85
Comments
What do you mean with "gradle classpath", normally dependencies are not inside some classpath? Can you add some build-script? |
ping @AstralStorm |
To build the project, you have to include JavaFX plugin in it in buildscript classpath. E.g. if I include it like this:
It checks for existence of JavaFX when included from system Java directories and not from gradle build script classpath and not when the task is running, so I cannot do:
nor
and are forced to patch JDK install in Android Studio which is highly inconvenient. Which should check if JavaFX is already in classpath(s) before attempting to add a potentially nonexistent jar file. (And potentially also if ant-javafx is in classpath.) |
As the JDK 9+ are not having the related classes anymore sitting in that JAR-file, I'm supposed to rework the whole thing, adding some additional flag for disabling this on JDK 8. First I was tempted to decline such idea, but as I'm forced to rework some parts I'm now fine with this idea ;) thanks for reporting and using this plugin. Only one drawback: I'm not able to custom-patch the class-files anymore for JDK 8 (but it's not possible for JDK 9+ anyway 😿 ) |
I'm adding some flag to disable adding |
Currently the plugin always attempts to find the jars on its own.
Modifying it to actually first check gradle classpath if it contains the required classes would allow including OpenJFX in the same build as a dependency.
Alternatively, some way of defining where it attempts to pull the JavaFX jars from would be required.
The text was updated successfully, but these errors were encountered: