Migrate JavaFX examples or retire them?

[keilw]

As we heard, Java 11 is not going to include JavaFX any more.

The JavaFX examples either have to be migrated to a successor project (Open FX or whatever) or retired over time if JavaFX itelf also ends up being archived.

[msgilligan]

I'm hearing that Java FX being decoupled from Java will be a good thing -- that it will evolve faster. Won't it just be an optional Maven dependency? By "migrate" do you just mean add the optional dependency?

[keilw]

Well it won't work with the JDK any more after Java 11. This is not a high prio issue since many people have not even moved to Java 7 but as soon as someone (@aalmiray hinted he'd love to help at the JavaLand unconference) establishes it in a new place after Oracle donated it (could take as long as NetBeans or JakartaEE) the dependency should be updated to ensure it'll work with any supported Java version.

[msgilligan]

Well it won't work with the JDK any more after Java 11

won't work with only the JDK any more after Java 11, right?

[aalmiray]

@msgilligan correct. OracleJDK 11 will ship without JavaFX. This is the same case as OpenJDK does right now, you must download OpenJFX as a separate binary. Starting with Java 11 we'll see releases of JavaFX that may or may not track the same release dates as OpenJDK; we're working on it.

[keilw]

@aalmiray Thanks for the input. Has the new place, namespace (e.g. if "javafx" may be preserved at least for existing modules like JakartaEE does) etc. been found already?

[keilw]

Marked it external because there is a dependency on a TBD JavaFX project.

[aalmiray]

No migration to a different space/brand is needed at the moment. JavaFX will continue being developed as part of the OpenJDK umbrella under OpenJFX.

[keilw]

If the community is allowed to do that like say DeviceIO (not sure, if that's still alive?) then it sounds like a good idea. Any chance you might get the RI of JSR 377 into that optional OJDK project or is Griffon the better option?

[aalmiray]

I think releasing an RI for JSR377 would be faster if Griffon is retrofitted with the new API rather than starting from scratch 😉

[keilw]

As long as the EC still exists and extends the lifeline (I see no Renewal Ballot 3 scheduled, but 13 months after the last one it should have been due by now) why not.

[Daniel-Dos]

Hello,

I'll do the migration / upgrade to OpenJavaFX 11.

in case I update it or create a new folder for it?