This seems reasonable to me as well: integrating the JavaFX modules into
whatever dependency manager you are using seems like a good thing.
-- Kevin
Johan Vos wrote:
Hi Michael,
The second question is what I think should be the default.
This is similar to Java EE ^^^ EE4J Jakarta
I think this feature would be nice to have but I doubt that it is simple
to achieve
because JavaFX may or may not already be included in the JDK against
which you build
and on which your project later runs. There needs to be a strategy how
to handle all
the resulting corner cases.
Am 28.02.18
Hi Kevin,
thank you for the update. I appreciate this work very much because I
think it is utterly important for JavaFX.
While reading the past messages again I was wondering whether this will
also address the following
two questions.
1. Will there be a way to determine at program start-up
"I mentioned our intention to make it easier for OpenJFX to be built,
tested, and run with OpenJDK builds that don't already contain javafx.*
modules."
+1 Great
On 2018-02-27T13:21:56 -0800
Kevin Rushforth wrote:
>
> In an earlier email with the subject "javafx might not be present" [1],
> I mentioned our intention to make it easier for OpenJFX to be built,
> tested, and run with OpenJDK builds that don't already contain