-
Notifications
You must be signed in to change notification settings - Fork 14
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
Component rule for JavaFX components #57
Comments
Is this something the maintainers of JavaFX need to do? |
Eventually yes. JavaFX could publish Gradle Metadata with the information I have sketched in this issue. Then Gradle users can depend on JavaFX components (or libraries building on top of JavaFX) without additional plugins and select the "JavaFX Platform Variant" by using the I now think a good start would be to add the rule to the official JavaFX plugin and have that use the attributes as well internally. Then the metadata publishing in JavaFX itself could be proposed as a next step. I made a proposal: openjfx/javafx-gradle-plugin#151 |
@johanvos Can you have a look? |
Thanks @jjohannes and @nlisker . openjfx/javafx-gradle-plugin#151 is merged. A potential next step is to see if we should do this in the openjfx repository itself. |
This is too interesting to not look at for me. 😄 I had a look at the JavaFX build and something like this should work: openjdk/jfx#1232 |
Closing as this rule has been directly added to |
JavaFX published OS/Arch specific Jars with classifiers. Would be great to add the corresponding variants with attributes, like in this example:
https://docs.gradle.org/current/userguide/component_metadata_rules.html#adding_variants_for_native_jars
Then it's straight forward to consume without using a JavaFX specific plugin or anything like that.
The rule looks roughly like this (need to double check OS/Arch values):
The text was updated successfully, but these errors were encountered: