Let me say for the record that I would prefer NetBeans to default to OpenJFX 11 or higher etc. I like anything we can do to encourage users to migrate from 8. However I believe dropping support for JavaFX 8 at this time would be a bad choice.
>>> It works out of the box. True... as of right now it successfully allows you to clean and build the app. However this was not the case until recently. The default setup is still missing aspects that would allow you to debug out of the box etc. My concern regarding the original question of this thread is that for many people using Java and JavaFX 8 in production, they are unsure if NetBeans 11.x is ready. They have yet to see a functioning example in NetBeans. I believe these users simply need "a little more time" to be comfortable with the transition, say 6 months or another minor release cycle. If support for JavaFX 8 were to be dropped right now, I fear a lot of these users would simply switch to intelliJ. Developers are a fickle bunch... I have some on my team that use intellij for our JavaFX apps simply because it works and they heard it was a good IDE. No other reason. Sean On Tue, Aug 27, 2019 at 12:09 AM Geertjan Wielenga <[email protected]> wrote: > It works out of the box. It is the openjfx.io POMs, e.g, this one: > > > https://github.com/openjfx/samples/blob/master/HelloFX/Maven/hellofx/pom.xml > > It would be great if you'd open an issue and then specify what exactly > needs to be in the POM for you, so that we can put it there for you so that > it will not be incomplete. > > https://issues.apache.org/jira/projects/NETBEANS > > Above is where you can now please, file an issue. Provide there the POM > that you would like to have. Can you do it, please? > > Gj > > On Tue, Aug 27, 2019 at 1:47 AM Kenneth Fogel <[email protected]> > wrote: > > > I think its worth keeping support for the old JavaFX that shipped in 8 > > thru 10 (I think it ended at 10). However it should not be the default. I > > was initially annoyed that there is not an updated pom.xml for OpenFX. > > Geertjan pointed out that there is an OpenFX project in the Samples group > > but its pom.xml appears incomplete. We could really use a flying squad > that > > examines every pom file that NetBeans adds to a project. They don't need > to > > be complex but there are certain plugins, i.e. Surefire, certain > > dependencies in some cases, and certain goals that should be present. The > > archetypes also need to be reviewed, I believe many are out of date. > > > > As for a quick fix, only have JavaFX as a choice under Ant if the default > > JDK is 8. The Maven and Graddle choices should only have OpenFX but have > a > > sample JavaFX project in the Samples essentially reversing the current > > setup.. > > > > Ken > > > > PS: By suggesting such an overhaul I am willing to work on it. > > > > > > > > -----Original Message----- > > From: Geertjan Wielenga <[email protected]> > > Sent: August 25, 2019 5:42 AM > > To: dev <[email protected]> > > Subject: What to do with JavaFX and OpenJFX? > > > > Hi all, > > > > What to do with JavaFX and OpenJFX? > > > > Should we continue making projects and samples available for JDK 8 JavaFX > > in the New Project dialog, because some users may be using JDK 8, or > should > > we only have projects and samples for OpenJFX in the New Project dialog? > > > > The full situation is described in detail here in a new blog entry I > wrote > > a few minutes ago: > > > > https://blogs.apache.org/netbeans/entry/what-to-do-with-javafx > > > > Thanks, > > > > Gj > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > >
