Re: Hopefully close to the finish line with Java 11 & FX

[Geertjan Wielenga]

On Sat, Sep 28, 2019 at 1:05 AM Scott Palmer  wrote:

> This is a good first step. I think some rough edges remain though.
>
> For example, if you go to the project properties ->Build->Compile and flip
> the JDK between Java from 8 to 11+, I’m guessing everything breaks. Can we
> do anything helpful in that situation?
>

Yes: https://github.com/openjfx/javafx-maven-plugin/pull/44

Are you going to comment in the above to add your voice to it?

Here is the related issue for NetBeans:

https://issues.apache.org/jira/browse/NETBEANS-3175

And the pull request:

https://github.com/apache/netbeans/pull/1535

Time to move from these lengthy e-mail discussions, I think we all agree
what the problem is, to moving towards a solution, via pull requests and
issues, i.e., the above, which are all ready for you to comment on and try
out, today.

Gj





>
> JavaFX 13 requires Java 11. What version of JavaFX is used by default when
> you pick a JDK 11 JavaFX project? I think it makes sense to default to the
> latest version that runs on Java 11., but rather than having two different
> project types for JavaFX, the new project wizard should have choices for
> JDK version (when more than one JDK is configured) and a selection for
> JavaFX version where the available options depend on the selected JDK
> version.
>
>
> Scott
>
> On Sep 27, 2019, at 11:09 AM, Geertjan Wielenga 
> wrote:
>
> 
> Also, please comment your support for this PR, which updates the Maven
> plugin for OpenJFX to support both JDK 8 and beyond:
>
> https://github.com/openjfx/javafx-maven-plugin/pull/44
>
> Gj
>
> On Fri, Sep 27, 2019 at 3:30 PM Geertjan Wielenga 
> wrote:
>
>>
>> On Fri, Sep 27, 2019 at 3:27 PM Chuck Davis  wrote:
>>
>>> I think that is a fabulous idea I've been advocating for since JDK11 was
>>> released.  What is on the "create a new project" menu needs to create a
>>> project that will build and run in the IDE.
>>>
>>
>> There is a very simple way to advocate anything at all with Maven and
>> NetBeans, just tweak this file whenever you have an improvement, new
>> archetypes, new versions, and provide a pull request. Just this file is all
>> you need, print it out and stick it on your ceiling so you see it whenever
>> you wake up in the morning:
>>
>>
>> https://github.com/apache/netbeans/blob/master/java/maven/src/org/netbeans/modules/maven/newproject/MavenWizardIterator.java
>>
>> Gj
>>
>>
>>
>>
>>>
>>> On Fri, Sep 27, 2019 at 7:24 AM Geertjan Wielenga 
>>> wrote:
>>>

 On Fri, Sep 27, 2019 at 3:21 PM Chuck Davis  wrote:

> I don't know what archetype should be "registered".  I just know what
> we've got doesn't work as expected by users.
>

 Great. So let's fix it. The idea would be to remove the "JavaFX
 Application" that is currently there and causing you so much headache.
 Instead of that, we'll have the two samples from Gluon there that are
 hidden right now in the Samples category.

 What do you think?

Re: Hopefully close to the finish line with Java 11 & FX

[Scott Palmer]

This is a good first step. I think some rough edges remain though. 

For example, if you go to the project properties ->Build->Compile and flip the 
JDK between Java from 8 to 11+, I’m guessing everything breaks. Can we do 
anything helpful in that situation?

JavaFX 13 requires Java 11. What version of JavaFX is used by default when you 
pick a JDK 11 JavaFX project? I think it makes sense to default to the latest 
version that runs on Java 11., but rather than having two different project 
types for JavaFX, the new project wizard should have choices for JDK version 
(when more than one JDK is configured) and a selection for JavaFX version where 
the available options depend on the selected JDK version. 


Scott

> On Sep 27, 2019, at 11:09 AM, Geertjan Wielenga  wrote:
> 
> 
> Also, please comment your support for this PR, which updates the Maven plugin 
> for OpenJFX to support both JDK 8 and beyond:
> 
> https://github.com/openjfx/javafx-maven-plugin/pull/44 
> 
> 
> Gj
> 
> On Fri, Sep 27, 2019 at 3:30 PM Geertjan Wielenga  > wrote:
> 
> On Fri, Sep 27, 2019 at 3:27 PM Chuck Davis  > wrote:
> I think that is a fabulous idea I've been advocating for since JDK11 was 
> released.  What is on the "create a new project" menu needs to create a 
> project that will build and run in the IDE.
> 
> There is a very simple way to advocate anything at all with Maven and 
> NetBeans, just tweak this file whenever you have an improvement, new 
> archetypes, new versions, and provide a pull request. Just this file is all 
> you need, print it out and stick it on your ceiling so you see it whenever 
> you wake up in the morning:
> 
> https://github.com/apache/netbeans/blob/master/java/maven/src/org/netbeans/modules/maven/newproject/MavenWizardIterator.java
>  
> 
> 
> Gj
> 
> 
>  
> 
> On Fri, Sep 27, 2019 at 7:24 AM Geertjan Wielenga  > wrote:
> 
> On Fri, Sep 27, 2019 at 3:21 PM Chuck Davis  > wrote:
> I don't know what archetype should be "registered".  I just know what we've 
> got doesn't work as expected by users.
> 
> Great. So let's fix it. The idea would be to remove the "JavaFX Application" 
> that is currently there and causing you so much headache. Instead of that, 
> we'll have the two samples from Gluon there that are hidden right now in the 
> Samples category.
> 
> What do you think?
> 

Re: Hopefully close to the finish line with Java 11 & FX

[Chuck Davis]

Done.

On Fri, Sep 27, 2019 at 8:09 AM Geertjan Wielenga 
wrote:

> Also, please comment your support for this PR, which updates the Maven
> plugin for OpenJFX to support both JDK 8 and beyond:
>
> https://github.com/openjfx/javafx-maven-plugin/pull/44
>
> Gj
>
>
>

Re: Hopefully close to the finish line with Java 11 & FX

[Geertjan Wielenga]

Also, please comment your support for this PR, which updates the Maven
plugin for OpenJFX to support both JDK 8 and beyond:

https://github.com/openjfx/javafx-maven-plugin/pull/44

Gj

On Fri, Sep 27, 2019 at 3:30 PM Geertjan Wielenga 
wrote:

>
> On Fri, Sep 27, 2019 at 3:27 PM Chuck Davis  wrote:
>
>> I think that is a fabulous idea I've been advocating for since JDK11 was
>> released.  What is on the "create a new project" menu needs to create a
>> project that will build and run in the IDE.
>>
>
> There is a very simple way to advocate anything at all with Maven and
> NetBeans, just tweak this file whenever you have an improvement, new
> archetypes, new versions, and provide a pull request. Just this file is all
> you need, print it out and stick it on your ceiling so you see it whenever
> you wake up in the morning:
>
>
> https://github.com/apache/netbeans/blob/master/java/maven/src/org/netbeans/modules/maven/newproject/MavenWizardIterator.java
>
> Gj
>
>
>
>
>>
>> On Fri, Sep 27, 2019 at 7:24 AM Geertjan Wielenga 
>> wrote:
>>
>>>
>>> On Fri, Sep 27, 2019 at 3:21 PM Chuck Davis  wrote:
>>>
 I don't know what archetype should be "registered".  I just know what
 we've got doesn't work as expected by users.

>>>
>>> Great. So let's fix it. The idea would be to remove the "JavaFX
>>> Application" that is currently there and causing you so much headache.
>>> Instead of that, we'll have the two samples from Gluon there that are
>>> hidden right now in the Samples category.
>>>
>>> What do you think?
>>>
>>>

Re: Hopefully close to the finish line with Java 11 & FX

[Geertjan Wielenga]

On Fri, Sep 27, 2019 at 3:27 PM Chuck Davis  wrote:

> I think that is a fabulous idea I've been advocating for since JDK11 was
> released.  What is on the "create a new project" menu needs to create a
> project that will build and run in the IDE.
>

There is a very simple way to advocate anything at all with Maven and
NetBeans, just tweak this file whenever you have an improvement, new
archetypes, new versions, and provide a pull request. Just this file is all
you need, print it out and stick it on your ceiling so you see it whenever
you wake up in the morning:

https://github.com/apache/netbeans/blob/master/java/maven/src/org/netbeans/modules/maven/newproject/MavenWizardIterator.java

Gj




>
> On Fri, Sep 27, 2019 at 7:24 AM Geertjan Wielenga 
> wrote:
>
>>
>> On Fri, Sep 27, 2019 at 3:21 PM Chuck Davis  wrote:
>>
>>> I don't know what archetype should be "registered".  I just know what
>>> we've got doesn't work as expected by users.
>>>
>>
>> Great. So let's fix it. The idea would be to remove the "JavaFX
>> Application" that is currently there and causing you so much headache.
>> Instead of that, we'll have the two samples from Gluon there that are
>> hidden right now in the Samples category.
>>
>> What do you think?
>>
>>

Re: Hopefully close to the finish line with Java 11 & FX

[Chuck Davis]

I think that is a fabulous idea I've been advocating for since JDK11 was
released.  What is on the "create a new project" menu needs to create a
project that will build and run in the IDE.

On Fri, Sep 27, 2019 at 7:24 AM Geertjan Wielenga 
wrote:

>
> On Fri, Sep 27, 2019 at 3:21 PM Chuck Davis  wrote:
>
>> I don't know what archetype should be "registered".  I just know what
>> we've got doesn't work as expected by users.
>>
>
> Great. So let's fix it. The idea would be to remove the "JavaFX
> Application" that is currently there and causing you so much headache.
> Instead of that, we'll have the two samples from Gluon there that are
> hidden right now in the Samples category.
>
> What do you think?
>
>

Re: Hopefully close to the finish line with Java 11 & FX

[Scott Palmer]

s to be done.
> 
> HTH with your frustrations.
> 
> On Fri, Sep 27, 2019 at 5:12 AM Chris Olsen  <mailto:col...@mchsi.com>> wrote:
> Scott and All --
> 
>   > The target should be 11 not 1.11. 
> 
>   Thanks to Scott!  I'm not sure where the 1.11 came from -- I think it was 
> generated somewhere out of my control.  (Yes, passing the buck.)
> 
>   In any case, one step forward has gotten me to another problem, which I 
> believe is with something called javafxpackager:
> 
> ---
>   Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
> (unpack-dependencies) on project Splat_Maven: Command execution failed. 
> Cannot run program "C:\Program 
> Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\..\bin\javafxpackager" (in directory 
> "C:\Users\olsenc\Documents\NetBeansProjects\Splat_Maven"): CreateProcess 
> error=2, The system cannot find the file specified -> [Help 1]
> ---
> 
>   In searching the web I found a great deal of only partially helpful 
> information, much related to Java 6 and 7.  Some places, in discussing Java 
> 11, seemed to suggest there was no longer in existence a javafxpackager, and 
> would there not be one until Java 14.  This is distressing, as my app is 
> replete with FX.  I wonder if someone could give me an authoritative answer 
> about what javafxpackager -- if it exists -- actually does.  I believe would 
> like to be able to deploy my app bundled with Java 11 in Windows and Mac 
> versions because of my target audience (high school teachers with even less 
> computer savvy that I have).  I'm beginning to think I should just return to 
> Java 8. I have solved many problems in migrating to Java 11, but I am getting 
> a bit discouraged when I contemplate the possibility of many problems still 
> to come, problems that suggest I should change professions from statistician 
> to Java developer -- not something I want to contemplate at this stage in my 
> career.
> 
>   Any advice for the harried and distraught _amateur_ programmer?
> 
>   Thank you in advance!
> 
>   -- Chris
> 
> 
> 
> 
> 
> - Original Message -
> From: Scott Palmer mailto:swpal...@gmail.com>>
> To: Chris Olsen mailto:col...@mchsi.com>>
> Cc: users@netbeans.apache.org <mailto:users@netbeans.apache.org>
> Sent: Tue, 24 Sep 2019 21:29:47 -0400 (EDT)
> Subject: Re: Hopefully close to the finish line with Java 11 & FX
> 
> The target should be 11 not 1.11. 
> 
> Scott
> 
> > On Sep 24, 2019, at 8:49 PM, Chris Olsen  > <mailto:col...@mchsi.com>> wrote:
> > 
> > Hello, Everyone --
> > 
> >   I have downloaded AdoptOpenJDK, JavaFX 11, and Maven (or so I believe).  
> > I have waded through getting to zero FX compile errors, and with the 
> > clarion call of "Excelcior!" I told Apache Netbeans 11.1 to run.  This is 
> > what I got:
> > 
> > 
> > Failed to execute goal 
> > org.apache.maven.plugins:maven-compiler-plugin:3.1:compile 
> > (default-compile) on project Splat_Maven: Fatal error compiling: error: 
> > invalid target release: 1.11 -> [Help 1] 
> > 
> > 
> >   I did my due diligence and looked for solutions on line, but nothing I 
> > found seemed to work.  What I'm thinking is that SOMEwhere I must have told 
> > some file or other that there is another Java 11 in town, but I don't 
> > really know where I would have said this.  (I blew away all my old Java 8 
> > JDKs.
> > 
> >   In hopes that this might give someone might have greater than zero clues, 
> > I am appending some System output below.  Any ideas of what and where to 
> > look for solutions and/or suggestions for how to proceed are very welcome!  
> > I'm running this on Windows 7, but my Windows 10 laptop gives the same 
> > "invalid target release" message.
> > 
> >   Thanks in advance...
> > 
> >   -- Chris Olsen
> > 
> > 
> > 
> > Echo %JAVA_HOME%:
> > 
> > C:\Program Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\
> > 
> > Echo %MAVEN_HOME%:
> > 
> > c:\Program Files\Maven\apache-maven-3.6.2-bin\apache-maven-3.6.2\bin
> > 
> > 
> > Path:
> > 
> > C:\Program 
> > Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\bin;C:\ProgramData\Oracle\Java\javapath;C:\Program
> >  Files 
> > (x86)\CambridgeSoft\ChemOffice2015\ChemScript\Lib;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Anaconda3;C:\Anaconda3\Scripts;C:\Program
> >  Files\M

Re: Hopefully close to the finish line with Java 11 & FX

[Geertjan Wielenga]

On Fri, Sep 27, 2019 at 3:24 PM Chuck Davis  wrote:

> If using a "sample" is required that should be indicated someplace where
> users will find it a project creation time.  I've been using NB for many
> years and have never had to resort to using a sample to create a project.
> It's not what a user would expect in my opinion.
>
>
Great, so go ahead and say how happy you are with this issue and pull
request, not here, but in the issue and pull request:

https://github.com/apache/netbeans/pull/1535

https://issues.apache.org/jira/browse/NETBEANS-3175

Gj



> If NB wants to maintain compatibility with JDK8 and JDK11+ then if two
> different archetypes are required we need two different project types --
> JFX for JDK8 and JFX for JDK11+.  ??
>
> On Fri, Sep 27, 2019 at 7:18 AM Geertjan Wielenga 
> wrote:
>
>>
>> Ideally, use the Gluon OpenJFX samples in the Sample category in the New
>> Project dialog -- and maybe we should replace the JavaFX Application with
>> those two samples instead?
>>
>>
>>

Re: Hopefully close to the finish line with Java 11 & FX

[Chuck Davis]

If using a "sample" is required that should be indicated someplace where
users will find it a project creation time.  I've been using NB for many
years and have never had to resort to using a sample to create a project.
It's not what a user would expect in my opinion.

If NB wants to maintain compatibility with JDK8 and JDK11+ then if two
different archetypes are required we need two different project types --
JFX for JDK8 and JFX for JDK11+.  ??

On Fri, Sep 27, 2019 at 7:18 AM Geertjan Wielenga 
wrote:

>
> Ideally, use the Gluon OpenJFX samples in the Sample category in the New
> Project dialog -- and maybe we should replace the JavaFX Application with
> those two samples instead?
>
>
>

Re: Hopefully close to the finish line with Java 11 & FX

[Geertjan Wielenga]

On Fri, Sep 27, 2019 at 3:21 PM Chuck Davis  wrote:

> I don't know what archetype should be "registered".  I just know what
> we've got doesn't work as expected by users.
>

Great. So let's fix it. The idea would be to remove the "JavaFX
Application" that is currently there and causing you so much headache.
Instead of that, we'll have the two samples from Gluon there that are
hidden right now in the Samples category.

What do you think?

Gj



>
> On Fri, Sep 27, 2019 at 7:13 AM Geertjan Wielenga 
> wrote:
>
>> Here is where that archetype is registered, is there another one we
>> should register instead:
>>
>>
>> https://github.com/apache/netbeans/blob/master/java/maven/src/org/netbeans/modules/maven/newproject/MavenWizardIterator.java
>>
>> See line 76 to 80 in the above.
>>
>> Gj
>>
>>
>> On Fri, Sep 27, 2019 at 3:10 PM Chuck Davis  wrote:
>>
>>> I don't think most users are going to build a project from samples (they
>>> expect what's on the menu to work).  Fortunately, I cared enough to find
>>> work-arounds people had posted on the internet but for new users it's a
>>> bombshell.
>>>
>>> On Fri, Sep 27, 2019 at 7:07 AM Geertjan Wielenga 
>>> wrote:
>>>
 Go to the Samples category in the New Project dialog and choose JavaFX.

Re: Hopefully close to the finish line with Java 11 & FX

[Geertjan Wielenga]

itch to enable full debug logging.
>>
>> For more information about the errors and possible solutions, please read
>> the following articles:
>> [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>
>>
>> On Sep 27, 2019, at 9:58 AM, Geertjan Wielenga 
>> wrote:
>>
>> The Gluon OpenJFX Maven sample archetypes have been part of Apache
>> NetBeans since 11.1.
>>
>> Gj
>>
>> On Fri, Sep 27, 2019 at 2:54 PM Chuck Davis  wrote:
>>
>>> Chris:
>>>
>>> NB has not made a JFX project that works since JDK8.  The JavaFX
>>> application should be taken off the new project menu until such time as it
>>> can build and run a JFX application.
>>>
>>> You might find some help here:  https://openjfx.io/openjfx-docs/#maven
>>>
>>> You can use NB to create the application but then you have to delete the
>>> entire pom and replace it with one that works -- which you will find at
>>> this link.  After you do that NB will actually run your application from
>>> the IDE.
>>>
>>> I recommend you build your dialogs with SceneBuilder outside the IDE for
>>> convenience.  One of the great features of fxml is reusability.  You can
>>> copy your fxml files into other projects, load them and nothing blows up.
>>> Since NB would not run a JFX application I wrote a script to copy the NB
>>> project files to another directory and run it there from a desktop icon.
>>> If you do that there are some tweaks to make for it to find the jfx
>>> modules.  I think you will also find  those issues addressed at the link
>>> but I don't remember for sure.  If you run into that you can email me
>>> off-list and we can discuss what has to be done.
>>>
>>> HTH with your frustrations.
>>>
>>> On Fri, Sep 27, 2019 at 5:12 AM Chris Olsen  wrote:
>>>
>>>> Scott and All --
>>>>
>>>>   > The target should be 11 not 1.11.
>>>>
>>>>   Thanks to Scott!  I'm not sure where the 1.11 came from -- I think it
>>>> was generated somewhere out of my control.  (Yes, passing the buck.)
>>>>
>>>>   In any case, one step forward has gotten me to another problem, which
>>>> I believe is with something called javafxpackager:
>>>>
>>>> ---
>>>>   Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>>> (unpack-dependencies) on project Splat_Maven: Command execution failed.
>>>> Cannot run program "C:\Program
>>>> Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\..\bin\javafxpackager" (in
>>>> directory "C:\Users\olsenc\Documents\NetBeansProjects\Splat_Maven"):
>>>> CreateProcess error=2, The system cannot find the file specified -> [Help 
>>>> 1]
>>>> ---
>>>>
>>>>   In searching the web I found a great deal of only partially helpful
>>>> information, much related to Java 6 and 7.  Some places, in discussing Java
>>>> 11, seemed to suggest there was no longer in existence a javafxpackager,
>>>> and would there not be one until Java 14.  This is distressing, as my app
>>>> is replete with FX.  I wonder if someone could give me an authoritative
>>>> answer about what javafxpackager -- if it exists -- actually does.  I
>>>> believe would like to be able to deploy my app bundled with Java 11 in
>>>> Windows and Mac versions because of my target audience (high school
>>>> teachers with even less computer savvy that I have).  I'm beginning to
>>>> think I should just return to Java 8. I have solved many problems in
>>>> migrating to Java 11, but I am getting a bit discouraged when I contemplate
>>>> the possibility of many problems still to come, problems that suggest I
>>>> should change professions from statistician to Java developer -- not
>>>> something I want to contemplate at this stage in my career.
>>>>
>>>>   Any advice for the harried and distraught _amateur_ programmer?
>>>>
>>>>   Thank you in advance!
>>>>
>>>>   -- Chris
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> - Original Message -
>>>> From: Scott Palmer 
>>>> To: Chris Olsen 
>>>> Cc: users@netbeans.apache.org
>>>> Sent: Tue, 24 Sep 2019 21:29:47 -0400 (EDT)
>>>> Subject: Re: Hope

Re: Hopefully close to the finish line with Java 11 & FX

[Chuck Davis]

I don't know what archetype should be "registered".  I just know what we've
got doesn't work as expected by users.

On Fri, Sep 27, 2019 at 7:13 AM Geertjan Wielenga 
wrote:

> Here is where that archetype is registered, is there another one we should
> register instead:
>
>
> https://github.com/apache/netbeans/blob/master/java/maven/src/org/netbeans/modules/maven/newproject/MavenWizardIterator.java
>
> See line 76 to 80 in the above.
>
> Gj
>
>
> On Fri, Sep 27, 2019 at 3:10 PM Chuck Davis  wrote:
>
>> I don't think most users are going to build a project from samples (they
>> expect what's on the menu to work).  Fortunately, I cared enough to find
>> work-arounds people had posted on the internet but for new users it's a
>> bombshell.
>>
>> On Fri, Sep 27, 2019 at 7:07 AM Geertjan Wielenga 
>> wrote:
>>
>>> Go to the Samples category in the New Project dialog and choose JavaFX.
>>>
>>>
>>>

Re: Hopefully close to the finish line with Java 11 & FX

[Geertjan Wielenga]

 -- which you will find at
>> this link.  After you do that NB will actually run your application from
>> the IDE.
>>
>> I recommend you build your dialogs with SceneBuilder outside the IDE for
>> convenience.  One of the great features of fxml is reusability.  You can
>> copy your fxml files into other projects, load them and nothing blows up.
>> Since NB would not run a JFX application I wrote a script to copy the NB
>> project files to another directory and run it there from a desktop icon.
>> If you do that there are some tweaks to make for it to find the jfx
>> modules.  I think you will also find  those issues addressed at the link
>> but I don't remember for sure.  If you run into that you can email me
>> off-list and we can discuss what has to be done.
>>
>> HTH with your frustrations.
>>
>> On Fri, Sep 27, 2019 at 5:12 AM Chris Olsen  wrote:
>>
>>> Scott and All --
>>>
>>>   > The target should be 11 not 1.11.
>>>
>>>   Thanks to Scott!  I'm not sure where the 1.11 came from -- I think it
>>> was generated somewhere out of my control.  (Yes, passing the buck.)
>>>
>>>   In any case, one step forward has gotten me to another problem, which
>>> I believe is with something called javafxpackager:
>>>
>>> ---
>>>   Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>> (unpack-dependencies) on project Splat_Maven: Command execution failed.
>>> Cannot run program "C:\Program
>>> Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\..\bin\javafxpackager" (in
>>> directory "C:\Users\olsenc\Documents\NetBeansProjects\Splat_Maven"):
>>> CreateProcess error=2, The system cannot find the file specified -> [Help 1]
>>> ---
>>>
>>>   In searching the web I found a great deal of only partially helpful
>>> information, much related to Java 6 and 7.  Some places, in discussing Java
>>> 11, seemed to suggest there was no longer in existence a javafxpackager,
>>> and would there not be one until Java 14.  This is distressing, as my app
>>> is replete with FX.  I wonder if someone could give me an authoritative
>>> answer about what javafxpackager -- if it exists -- actually does.  I
>>> believe would like to be able to deploy my app bundled with Java 11 in
>>> Windows and Mac versions because of my target audience (high school
>>> teachers with even less computer savvy that I have).  I'm beginning to
>>> think I should just return to Java 8. I have solved many problems in
>>> migrating to Java 11, but I am getting a bit discouraged when I contemplate
>>> the possibility of many problems still to come, problems that suggest I
>>> should change professions from statistician to Java developer -- not
>>> something I want to contemplate at this stage in my career.
>>>
>>>   Any advice for the harried and distraught _amateur_ programmer?
>>>
>>>   Thank you in advance!
>>>
>>>   -- Chris
>>>
>>>
>>>
>>>
>>>
>>> - Original Message -
>>> From: Scott Palmer 
>>> To: Chris Olsen 
>>> Cc: users@netbeans.apache.org
>>> Sent: Tue, 24 Sep 2019 21:29:47 -0400 (EDT)
>>> Subject: Re: Hopefully close to the finish line with Java 11 & FX
>>>
>>> The target should be 11 not 1.11.
>>>
>>> Scott
>>>
>>> > On Sep 24, 2019, at 8:49 PM, Chris Olsen  wrote:
>>> >
>>> > Hello, Everyone --
>>> >
>>> >   I have downloaded AdoptOpenJDK, JavaFX 11, and Maven (or so I
>>> believe).  I have waded through getting to zero FX compile errors, and with
>>> the clarion call of "Excelcior!" I told Apache Netbeans 11.1 to run.  This
>>> is what I got:
>>> >
>>> > 
>>> > Failed to execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
>>> (default-compile) on project Splat_Maven: Fatal error compiling: error:
>>> invalid target release: 1.11 -> [Help 1]
>>> > 
>>> >
>>> >   I did my due diligence and looked for solutions on line, but nothing
>>> I found seemed to work.  What I'm thinking is that SOMEwhere I must have
>>> told some file or other that there is another Java 11 in town, but I don't
>>> really know where I would have said this.  (I blew away all my old Java 8
>>> JDKs.
>>> >
>>> > 

Re: Hopefully close to the finish line with Java 11 & FX

[Geertjan Wielenga]

Here is where that archetype is registered, is there another one we should
register instead:

https://github.com/apache/netbeans/blob/master/java/maven/src/org/netbeans/modules/maven/newproject/MavenWizardIterator.java

See line 76 to 80 in the above.

Gj


On Fri, Sep 27, 2019 at 3:10 PM Chuck Davis  wrote:

> I don't think most users are going to build a project from samples (they
> expect what's on the menu to work).  Fortunately, I cared enough to find
> work-arounds people had posted on the internet but for new users it's a
> bombshell.
>
> On Fri, Sep 27, 2019 at 7:07 AM Geertjan Wielenga 
> wrote:
>
>> Go to the Samples category in the New Project dialog and choose JavaFX.
>>
>>
>>

Re: Hopefully close to the finish line with Java 11 & FX

[Chuck Davis]

I don't think most users are going to build a project from samples (they
expect what's on the menu to work).  Fortunately, I cared enough to find
work-arounds people had posted on the internet but for new users it's a
bombshell.

On Fri, Sep 27, 2019 at 7:07 AM Geertjan Wielenga 
wrote:

> Go to the Samples category in the New Project dialog and choose JavaFX.
>
>
>

Re: Hopefully close to the finish line with Java 11 & FX

[Geertjan Wielenga]

Go to the Samples category in the New Project dialog and choose JavaFX.

Gj

On Fri, Sep 27, 2019 at 3:04 PM Chuck Davis  wrote:

> That would be a good motive to move to Gradle!!
>
> On Fri, Sep 27, 2019 at 7:00 AM Scott Palmer  wrote:
>
>> You can also easily make a JavaFX project with NetBeans if you use a
>> Gradle project - as everyone should ;-)
>>
>> https://openjfx.io/openjfx-docs/#gradle
>>
>> But you do have to manually add the javafx-plugin to your Gradle build
>> script.  Perhaps we can get that fixed with a tweak to the new project
>> wizard for Gradle-based projects.
>>
>> Scott
>>
>>
>> On Sep 27, 2019, at 9:47 AM, Chuck Davis  wrote:
>>
>> Chris:
>>
>> NB has not made a JFX project that works since JDK8.  The JavaFX
>> application should be taken off the new project menu until such time as it
>> can build and run a JFX application.
>>
>> You might find some help here:  https://openjfx.io/openjfx-docs/#maven
>>
>> You can use NB to create the application but then you have to delete the
>> entire pom and replace it with one that works -- which you will find at
>> this link.  After you do that NB will actually run your application from
>> the IDE.
>>
>> I recommend you build your dialogs with SceneBuilder outside the IDE for
>> convenience.  One of the great features of fxml is reusability.  You can
>> copy your fxml files into other projects, load them and nothing blows up.
>> Since NB would not run a JFX application I wrote a script to copy the NB
>> project files to another directory and run it there from a desktop icon.
>> If you do that there are some tweaks to make for it to find the jfx
>> modules.  I think you will also find  those issues addressed at the link
>> but I don't remember for sure.  If you run into that you can email me
>> off-list and we can discuss what has to be done.
>>
>> HTH with your frustrations.
>>
>> On Fri, Sep 27, 2019 at 5:12 AM Chris Olsen  wrote:
>>
>>> Scott and All --
>>>
>>>   > The target should be 11 not 1.11.
>>>
>>>   Thanks to Scott!  I'm not sure where the 1.11 came from -- I think it
>>> was generated somewhere out of my control.  (Yes, passing the buck.)
>>>
>>>   In any case, one step forward has gotten me to another problem, which
>>> I believe is with something called javafxpackager:
>>>
>>> ---
>>>   Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>> (unpack-dependencies) on project Splat_Maven: Command execution failed.
>>> Cannot run program "C:\Program
>>> Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\..\bin\javafxpackager" (in
>>> directory "C:\Users\olsenc\Documents\NetBeansProjects\Splat_Maven"):
>>> CreateProcess error=2, The system cannot find the file specified -> [Help 1]
>>> ---
>>>
>>>   In searching the web I found a great deal of only partially helpful
>>> information, much related to Java 6 and 7.  Some places, in discussing Java
>>> 11, seemed to suggest there was no longer in existence a javafxpackager,
>>> and would there not be one until Java 14.  This is distressing, as my app
>>> is replete with FX.  I wonder if someone could give me an authoritative
>>> answer about what javafxpackager -- if it exists -- actually does.  I
>>> believe would like to be able to deploy my app bundled with Java 11 in
>>> Windows and Mac versions because of my target audience (high school
>>> teachers with even less computer savvy that I have).  I'm beginning to
>>> think I should just return to Java 8. I have solved many problems in
>>> migrating to Java 11, but I am getting a bit discouraged when I contemplate
>>> the possibility of many problems still to come, problems that suggest I
>>> should change professions from statistician to Java developer -- not
>>> something I want to contemplate at this stage in my career.
>>>
>>>   Any advice for the harried and distraught _amateur_ programmer?
>>>
>>>   Thank you in advance!
>>>
>>>   -- Chris
>>>
>>>
>>>
>>>
>>>
>>> - Original Message -
>>> From: Scott Palmer 
>>> To: Chris Olsen 
>>> Cc: users@netbeans.apache.org
>>> Sent: Tue, 24 Sep 2019 21:29:47 -0400 (EDT)
>>> Subject: Re: Hopefully close to the finish line with Java 11 & FX
>>>
>>> The target should be 11 not 1.11.
>>>
>>>

Re: Hopefully close to the finish line with Java 11 & FX

[Chuck Davis]

That would be a good motive to move to Gradle!!

On Fri, Sep 27, 2019 at 7:00 AM Scott Palmer  wrote:

> You can also easily make a JavaFX project with NetBeans if you use a
> Gradle project - as everyone should ;-)
>
> https://openjfx.io/openjfx-docs/#gradle
>
> But you do have to manually add the javafx-plugin to your Gradle build
> script.  Perhaps we can get that fixed with a tweak to the new project
> wizard for Gradle-based projects.
>
> Scott
>
>
> On Sep 27, 2019, at 9:47 AM, Chuck Davis  wrote:
>
> Chris:
>
> NB has not made a JFX project that works since JDK8.  The JavaFX
> application should be taken off the new project menu until such time as it
> can build and run a JFX application.
>
> You might find some help here:  https://openjfx.io/openjfx-docs/#maven
>
> You can use NB to create the application but then you have to delete the
> entire pom and replace it with one that works -- which you will find at
> this link.  After you do that NB will actually run your application from
> the IDE.
>
> I recommend you build your dialogs with SceneBuilder outside the IDE for
> convenience.  One of the great features of fxml is reusability.  You can
> copy your fxml files into other projects, load them and nothing blows up.
> Since NB would not run a JFX application I wrote a script to copy the NB
> project files to another directory and run it there from a desktop icon.
> If you do that there are some tweaks to make for it to find the jfx
> modules.  I think you will also find  those issues addressed at the link
> but I don't remember for sure.  If you run into that you can email me
> off-list and we can discuss what has to be done.
>
> HTH with your frustrations.
>
> On Fri, Sep 27, 2019 at 5:12 AM Chris Olsen  wrote:
>
>> Scott and All --
>>
>>   > The target should be 11 not 1.11.
>>
>>   Thanks to Scott!  I'm not sure where the 1.11 came from -- I think it
>> was generated somewhere out of my control.  (Yes, passing the buck.)
>>
>>   In any case, one step forward has gotten me to another problem, which I
>> believe is with something called javafxpackager:
>>
>> ---
>>   Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>> (unpack-dependencies) on project Splat_Maven: Command execution failed.
>> Cannot run program "C:\Program
>> Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\..\bin\javafxpackager" (in
>> directory "C:\Users\olsenc\Documents\NetBeansProjects\Splat_Maven"):
>> CreateProcess error=2, The system cannot find the file specified -> [Help 1]
>> ---
>>
>>   In searching the web I found a great deal of only partially helpful
>> information, much related to Java 6 and 7.  Some places, in discussing Java
>> 11, seemed to suggest there was no longer in existence a javafxpackager,
>> and would there not be one until Java 14.  This is distressing, as my app
>> is replete with FX.  I wonder if someone could give me an authoritative
>> answer about what javafxpackager -- if it exists -- actually does.  I
>> believe would like to be able to deploy my app bundled with Java 11 in
>> Windows and Mac versions because of my target audience (high school
>> teachers with even less computer savvy that I have).  I'm beginning to
>> think I should just return to Java 8. I have solved many problems in
>> migrating to Java 11, but I am getting a bit discouraged when I contemplate
>> the possibility of many problems still to come, problems that suggest I
>> should change professions from statistician to Java developer -- not
>> something I want to contemplate at this stage in my career.
>>
>>   Any advice for the harried and distraught _amateur_ programmer?
>>
>>   Thank you in advance!
>>
>>   -- Chris
>>
>>
>>
>>
>>
>> - Original Message -
>> From: Scott Palmer 
>> To: Chris Olsen 
>> Cc: users@netbeans.apache.org
>> Sent: Tue, 24 Sep 2019 21:29:47 -0400 (EDT)
>> Subject: Re: Hopefully close to the finish line with Java 11 & FX
>>
>> The target should be 11 not 1.11.
>>
>> Scott
>>
>> > On Sep 24, 2019, at 8:49 PM, Chris Olsen  wrote:
>> >
>> > Hello, Everyone --
>> >
>> >   I have downloaded AdoptOpenJDK, JavaFX 11, and Maven (or so I
>> believe).  I have waded through getting to zero FX compile errors, and with
>> the clarion call of "Excelcior!" I told Apache Netbeans 11.1 to run.  This
>> is what I got:
>> >
>> > 
>> > Failed to execute goal
>> org.apache.maven.

Re: Hopefully close to the finish line with Java 11 & FX

[Chuck Davis]

I should have added "that compiles" under JDK 12.  It may still work with
JDK 8 -- don't know.

On Fri, Sep 27, 2019 at 7:00 AM Chuck Davis  wrote:

> I just tried it a few minutes ago to be sure it hadn't been fixed.  NB
> 11.1 does NOT create a JFX application that compiles.
>
>
>

Re: Hopefully close to the finish line with Java 11 & FX

[Chuck Davis]

I just tried it a few minutes ago to be sure it hadn't been fixed.  NB 11.1
does NOT create a JFX application that compiles.

On Fri, Sep 27, 2019 at 6:58 AM Geertjan Wielenga 
wrote:

> The Gluon OpenJFX Maven sample archetypes have been part of Apache
> NetBeans since 11.1.
>
> Gj
>
> On Fri, Sep 27, 2019 at 2:54 PM Chuck Davis  wrote:
>
>> Chris:
>>
>> NB has not made a JFX project that works since JDK8.  The JavaFX
>> application should be taken off the new project menu until such time as it
>> can build and run a JFX application.
>>
>> You might find some help here:  https://openjfx.io/openjfx-docs/#maven
>>
>> You can use NB to create the application but then you have to delete the
>> entire pom and replace it with one that works -- which you will find at
>> this link.  After you do that NB will actually run your application from
>> the IDE.
>>
>> I recommend you build your dialogs with SceneBuilder outside the IDE for
>> convenience.  One of the great features of fxml is reusability.  You can
>> copy your fxml files into other projects, load them and nothing blows up.
>> Since NB would not run a JFX application I wrote a script to copy the NB
>> project files to another directory and run it there from a desktop icon.
>> If you do that there are some tweaks to make for it to find the jfx
>> modules.  I think you will also find  those issues addressed at the link
>> but I don't remember for sure.  If you run into that you can email me
>> off-list and we can discuss what has to be done.
>>
>> HTH with your frustrations.
>>
>> On Fri, Sep 27, 2019 at 5:12 AM Chris Olsen  wrote:
>>
>>> Scott and All --
>>>
>>>   > The target should be 11 not 1.11.
>>>
>>>   Thanks to Scott!  I'm not sure where the 1.11 came from -- I think it
>>> was generated somewhere out of my control.  (Yes, passing the buck.)
>>>
>>>   In any case, one step forward has gotten me to another problem, which
>>> I believe is with something called javafxpackager:
>>>
>>> ---
>>>   Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>>> (unpack-dependencies) on project Splat_Maven: Command execution failed.
>>> Cannot run program "C:\Program
>>> Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\..\bin\javafxpackager" (in
>>> directory "C:\Users\olsenc\Documents\NetBeansProjects\Splat_Maven"):
>>> CreateProcess error=2, The system cannot find the file specified -> [Help 1]
>>> ---
>>>
>>>   In searching the web I found a great deal of only partially helpful
>>> information, much related to Java 6 and 7.  Some places, in discussing Java
>>> 11, seemed to suggest there was no longer in existence a javafxpackager,
>>> and would there not be one until Java 14.  This is distressing, as my app
>>> is replete with FX.  I wonder if someone could give me an authoritative
>>> answer about what javafxpackager -- if it exists -- actually does.  I
>>> believe would like to be able to deploy my app bundled with Java 11 in
>>> Windows and Mac versions because of my target audience (high school
>>> teachers with even less computer savvy that I have).  I'm beginning to
>>> think I should just return to Java 8. I have solved many problems in
>>> migrating to Java 11, but I am getting a bit discouraged when I contemplate
>>> the possibility of many problems still to come, problems that suggest I
>>> should change professions from statistician to Java developer -- not
>>> something I want to contemplate at this stage in my career.
>>>
>>>   Any advice for the harried and distraught _amateur_ programmer?
>>>
>>>   Thank you in advance!
>>>
>>>   -- Chris
>>>
>>>
>>>
>>>
>>>
>>> - Original Message -
>>> From: Scott Palmer 
>>> To: Chris Olsen 
>>> Cc: users@netbeans.apache.org
>>> Sent: Tue, 24 Sep 2019 21:29:47 -0400 (EDT)
>>> Subject: Re: Hopefully close to the finish line with Java 11 & FX
>>>
>>> The target should be 11 not 1.11.
>>>
>>> Scott
>>>
>>> > On Sep 24, 2019, at 8:49 PM, Chris Olsen  wrote:
>>> >
>>> > Hello, Everyone --
>>> >
>>> >   I have downloaded AdoptOpenJDK, JavaFX 11, and Maven (or so I
>>> believe).  I have waded through getting to zero FX compile errors, and with
>>> the clarion call of "Excelcior!"

Re: Hopefully close to the finish line with Java 11 & FX

[Scott Palmer]

You can also easily make a JavaFX project with NetBeans if you use a Gradle 
project - as everyone should ;-)

https://openjfx.io/openjfx-docs/#gradle 
<https://openjfx.io/openjfx-docs/#gradle>

But you do have to manually add the javafx-plugin to your Gradle build script.  
Perhaps we can get that fixed with a tweak to the new project wizard for 
Gradle-based projects.

Scott


> On Sep 27, 2019, at 9:47 AM, Chuck Davis  wrote:
> 
> Chris:
> 
> NB has not made a JFX project that works since JDK8.  The JavaFX application 
> should be taken off the new project menu until such time as it can build and 
> run a JFX application.  
> 
> You might find some help here:  https://openjfx.io/openjfx-docs/#maven 
> <https://openjfx.io/openjfx-docs/#maven>
> 
> You can use NB to create the application but then you have to delete the 
> entire pom and replace it with one that works -- which you will find at this 
> link.  After you do that NB will actually run your application from the IDE.
> 
> I recommend you build your dialogs with SceneBuilder outside the IDE for 
> convenience.  One of the great features of fxml is reusability.  You can copy 
> your fxml files into other projects, load them and nothing blows up.  Since 
> NB would not run a JFX application I wrote a script to copy the NB project 
> files to another directory and run it there from a desktop icon.  If you do 
> that there are some tweaks to make for it to find the jfx modules.  I think 
> you will also find  those issues addressed at the link but I don't remember 
> for sure.  If you run into that you can email me off-list and we can discuss 
> what has to be done.
> 
> HTH with your frustrations.
> 
> On Fri, Sep 27, 2019 at 5:12 AM Chris Olsen  <mailto:col...@mchsi.com>> wrote:
> Scott and All --
> 
>   > The target should be 11 not 1.11. 
> 
>   Thanks to Scott!  I'm not sure where the 1.11 came from -- I think it was 
> generated somewhere out of my control.  (Yes, passing the buck.)
> 
>   In any case, one step forward has gotten me to another problem, which I 
> believe is with something called javafxpackager:
> 
> ---
>   Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
> (unpack-dependencies) on project Splat_Maven: Command execution failed. 
> Cannot run program "C:\Program 
> Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\..\bin\javafxpackager" (in directory 
> "C:\Users\olsenc\Documents\NetBeansProjects\Splat_Maven"): CreateProcess 
> error=2, The system cannot find the file specified -> [Help 1]
> ---
> 
>   In searching the web I found a great deal of only partially helpful 
> information, much related to Java 6 and 7.  Some places, in discussing Java 
> 11, seemed to suggest there was no longer in existence a javafxpackager, and 
> would there not be one until Java 14.  This is distressing, as my app is 
> replete with FX.  I wonder if someone could give me an authoritative answer 
> about what javafxpackager -- if it exists -- actually does.  I believe would 
> like to be able to deploy my app bundled with Java 11 in Windows and Mac 
> versions because of my target audience (high school teachers with even less 
> computer savvy that I have).  I'm beginning to think I should just return to 
> Java 8. I have solved many problems in migrating to Java 11, but I am getting 
> a bit discouraged when I contemplate the possibility of many problems still 
> to come, problems that suggest I should change professions from statistician 
> to Java developer -- not something I want to contemplate at this stage in my 
> career.
> 
>   Any advice for the harried and distraught _amateur_ programmer?
> 
>   Thank you in advance!
> 
>   -- Chris
> 
> 
> 
> 
> 
> ----- Original Message -
> From: Scott Palmer mailto:swpal...@gmail.com>>
> To: Chris Olsen mailto:col...@mchsi.com>>
> Cc: users@netbeans.apache.org <mailto:users@netbeans.apache.org>
> Sent: Tue, 24 Sep 2019 21:29:47 -0400 (EDT)
> Subject: Re: Hopefully close to the finish line with Java 11 & FX
> 
> The target should be 11 not 1.11. 
> 
> Scott
> 
> > On Sep 24, 2019, at 8:49 PM, Chris Olsen  > <mailto:col...@mchsi.com>> wrote:
> > 
> > Hello, Everyone --
> > 
> >   I have downloaded AdoptOpenJDK, JavaFX 11, and Maven (or so I believe).  
> > I have waded through getting to zero FX compile errors, and with the 
> > clarion call of "Excelcior!" I told Apache Netbeans 11.1 to run.  This is 
> > what I got:
> > 
> > 
> > Failed to execute goal 
> > org.apache.maven.plugins:maven-compiler-plugin:3.1:compile 
> > (default-comp

Re: Hopefully close to the finish line with Java 11 & FX

[Chuck Davis]

Scott, glad to hear I'm not the only one with major headaches.  Java 8 and
Java 11 are such vastly different creatures I don't see how anyone would
expect NB to address both equally well.  It militates for a break in
compatibility with the IDE in my opinion.  Those who want to stay on Java 8
can continue using NB 11.  Those of us who move forward should not be held
back by an antiquated IDE that tries to live in two entirely different
worlds.

On Fri, Sep 27, 2019 at 6:45 AM Scott Palmer  wrote:

> Javafxpackager was removed along with several other things in Java 11.
> Sadly this was done with no reasonable path forward - there was no
> replacement for javapackager (it was renamed from javafxpackager because it
> isn’t strictly related to JavaFX), nor were many of the removed modules
> available with modular replacements (they were passed off to other open
> source communities to deal with, and those communities completely dropped
> the ball - Eclipse people I’m looking at you).
>
>
> Anyway.. the new jpackage tool, that was originally intended for Java 13
> and now is expected as an experimental feature of Java 14, is available as
> a pre-release and can be used to package an application with Java 11.
>
> You can get the early-access build from here
> https://jdk.java.net/jpackage/
>
> jpackage is a tool that will create a native installer for Windows, or a
> package for Linux or macOS, or just an application image.  It includes your
> application and the JRE required to run it, all nicely bundled together so
> it appears as any other platform-specific application.
>
> The new jpackage tool serves the same purpose as javafxpackager, but it is
> not compatible.  The options have changed.
>
> It may be an adventure getting your project working.  I’ve been there… the
> transition away from Java 8 has been a massive headache for this and a few
> other reasons.
>
> Regards,
>
> Scott
>
>
> On Sep 27, 2019, at 8:02 AM, Chris Olsen  wrote:
>
> Scott and All --
>
> The target should be 11 not 1.11.
>
>
>  Thanks to Scott!  I'm not sure where the 1.11 came from -- I think it was
> generated somewhere out of my control.  (Yes, passing the buck.)
>
>  In any case, one step forward has gotten me to another problem, which I
> believe is with something called javafxpackager:
>
> ---
>  Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
> (unpack-dependencies) on project Splat_Maven: Command execution failed.
> Cannot run program "C:\Program
> Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\..\bin\javafxpackager" (in
> directory "C:\Users\olsenc\Documents\NetBeansProjects\Splat_Maven"):
> CreateProcess error=2, The system cannot find the file specified -> [Help 1]
> ---
>
>  In searching the web I found a great deal of only partially helpful
> information, much related to Java 6 and 7.  Some places, in discussing Java
> 11, seemed to suggest there was no longer in existence a javafxpackager,
> and would there not be one until Java 14.  This is distressing, as my app
> is replete with FX.  I wonder if someone could give me an authoritative
> answer about what javafxpackager -- if it exists -- actually does.  I
> believe would like to be able to deploy my app bundled with Java 11 in
> Windows and Mac versions because of my target audience (high school
> teachers with even less computer savvy that I have).  I'm beginning to
> think I should just return to Java 8. I have solved many problems in
> migrating to Java 11, but I am getting a bit discouraged when I contemplate
> the possibility of many problems still to come, problems that suggest I
> should change professions from statistician to Java developer -- not
> something I want to contemplate at this stage in my career.
>
>  Any advice for the harried and distraught _amateur_ programmer?
>
>  Thank you in advance!
>
>  -- Chris
>
>
>
>
>
> - Original Message -
> From: Scott Palmer 
> To: Chris Olsen 
> Cc: users@netbeans.apache.org
> Sent: Tue, 24 Sep 2019 21:29:47 -0400 (EDT)
> Subject: Re: Hopefully close to the finish line with Java 11 & FX
>
> The target should be 11 not 1.11.
>
> Scott
>
> On Sep 24, 2019, at 8:49 PM, Chris Olsen  wrote:
>
> Hello, Everyone --
>
>  I have downloaded AdoptOpenJDK, JavaFX 11, and Maven (or so I believe).
> I have waded through getting to zero FX compile errors, and with the
> clarion call of "Excelcior!" I told Apache Netbeans 11.1 to run.  This is
> what I got:
>
> 
> Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
> (default-compile) on project Splat_Maven: Fatal error compiling: 

Re: Hopefully close to the finish line with Java 11 & FX

[Geertjan Wielenga]

The Gluon OpenJFX Maven sample archetypes have been part of Apache NetBeans
since 11.1.

Gj

On Fri, Sep 27, 2019 at 2:54 PM Chuck Davis  wrote:

> Chris:
>
> NB has not made a JFX project that works since JDK8.  The JavaFX
> application should be taken off the new project menu until such time as it
> can build and run a JFX application.
>
> You might find some help here:  https://openjfx.io/openjfx-docs/#maven
>
> You can use NB to create the application but then you have to delete the
> entire pom and replace it with one that works -- which you will find at
> this link.  After you do that NB will actually run your application from
> the IDE.
>
> I recommend you build your dialogs with SceneBuilder outside the IDE for
> convenience.  One of the great features of fxml is reusability.  You can
> copy your fxml files into other projects, load them and nothing blows up.
> Since NB would not run a JFX application I wrote a script to copy the NB
> project files to another directory and run it there from a desktop icon.
> If you do that there are some tweaks to make for it to find the jfx
> modules.  I think you will also find  those issues addressed at the link
> but I don't remember for sure.  If you run into that you can email me
> off-list and we can discuss what has to be done.
>
> HTH with your frustrations.
>
> On Fri, Sep 27, 2019 at 5:12 AM Chris Olsen  wrote:
>
>> Scott and All --
>>
>>   > The target should be 11 not 1.11.
>>
>>   Thanks to Scott!  I'm not sure where the 1.11 came from -- I think it
>> was generated somewhere out of my control.  (Yes, passing the buck.)
>>
>>   In any case, one step forward has gotten me to another problem, which I
>> believe is with something called javafxpackager:
>>
>> ---
>>   Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
>> (unpack-dependencies) on project Splat_Maven: Command execution failed.
>> Cannot run program "C:\Program
>> Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\..\bin\javafxpackager" (in
>> directory "C:\Users\olsenc\Documents\NetBeansProjects\Splat_Maven"):
>> CreateProcess error=2, The system cannot find the file specified -> [Help 1]
>> ---
>>
>>   In searching the web I found a great deal of only partially helpful
>> information, much related to Java 6 and 7.  Some places, in discussing Java
>> 11, seemed to suggest there was no longer in existence a javafxpackager,
>> and would there not be one until Java 14.  This is distressing, as my app
>> is replete with FX.  I wonder if someone could give me an authoritative
>> answer about what javafxpackager -- if it exists -- actually does.  I
>> believe would like to be able to deploy my app bundled with Java 11 in
>> Windows and Mac versions because of my target audience (high school
>> teachers with even less computer savvy that I have).  I'm beginning to
>> think I should just return to Java 8. I have solved many problems in
>> migrating to Java 11, but I am getting a bit discouraged when I contemplate
>> the possibility of many problems still to come, problems that suggest I
>> should change professions from statistician to Java developer -- not
>> something I want to contemplate at this stage in my career.
>>
>>   Any advice for the harried and distraught _amateur_ programmer?
>>
>>   Thank you in advance!
>>
>>   -- Chris
>>
>>
>>
>>
>>
>> - Original Message -
>> From: Scott Palmer 
>> To: Chris Olsen 
>> Cc: users@netbeans.apache.org
>> Sent: Tue, 24 Sep 2019 21:29:47 -0400 (EDT)
>> Subject: Re: Hopefully close to the finish line with Java 11 & FX
>>
>> The target should be 11 not 1.11.
>>
>> Scott
>>
>> > On Sep 24, 2019, at 8:49 PM, Chris Olsen  wrote:
>> >
>> > Hello, Everyone --
>> >
>> >   I have downloaded AdoptOpenJDK, JavaFX 11, and Maven (or so I
>> believe).  I have waded through getting to zero FX compile errors, and with
>> the clarion call of "Excelcior!" I told Apache Netbeans 11.1 to run.  This
>> is what I got:
>> >
>> > 
>> > Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
>> (default-compile) on project Splat_Maven: Fatal error compiling: error:
>> invalid target release: 1.11 -> [Help 1]
>> > 
>> >
>> >   I did my due diligence and looked for solutions on line, but nothing
>> I found seemed to work.  What I'm thinking is that SOMEwhere I must have
>> told some fi

Re: Hopefully close to the finish line with Java 11 & FX

[Chuck Davis]

Chris:

NB has not made a JFX project that works since JDK8.  The JavaFX
application should be taken off the new project menu until such time as it
can build and run a JFX application.

You might find some help here:  https://openjfx.io/openjfx-docs/#maven

You can use NB to create the application but then you have to delete the
entire pom and replace it with one that works -- which you will find at
this link.  After you do that NB will actually run your application from
the IDE.

I recommend you build your dialogs with SceneBuilder outside the IDE for
convenience.  One of the great features of fxml is reusability.  You can
copy your fxml files into other projects, load them and nothing blows up.
Since NB would not run a JFX application I wrote a script to copy the NB
project files to another directory and run it there from a desktop icon.
If you do that there are some tweaks to make for it to find the jfx
modules.  I think you will also find  those issues addressed at the link
but I don't remember for sure.  If you run into that you can email me
off-list and we can discuss what has to be done.

HTH with your frustrations.

On Fri, Sep 27, 2019 at 5:12 AM Chris Olsen  wrote:

> Scott and All --
>
>   > The target should be 11 not 1.11.
>
>   Thanks to Scott!  I'm not sure where the 1.11 came from -- I think it
> was generated somewhere out of my control.  (Yes, passing the buck.)
>
>   In any case, one step forward has gotten me to another problem, which I
> believe is with something called javafxpackager:
>
> ---
>   Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
> (unpack-dependencies) on project Splat_Maven: Command execution failed.
> Cannot run program "C:\Program
> Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\..\bin\javafxpackager" (in
> directory "C:\Users\olsenc\Documents\NetBeansProjects\Splat_Maven"):
> CreateProcess error=2, The system cannot find the file specified -> [Help 1]
> ---
>
>   In searching the web I found a great deal of only partially helpful
> information, much related to Java 6 and 7.  Some places, in discussing Java
> 11, seemed to suggest there was no longer in existence a javafxpackager,
> and would there not be one until Java 14.  This is distressing, as my app
> is replete with FX.  I wonder if someone could give me an authoritative
> answer about what javafxpackager -- if it exists -- actually does.  I
> believe would like to be able to deploy my app bundled with Java 11 in
> Windows and Mac versions because of my target audience (high school
> teachers with even less computer savvy that I have).  I'm beginning to
> think I should just return to Java 8. I have solved many problems in
> migrating to Java 11, but I am getting a bit discouraged when I contemplate
> the possibility of many problems still to come, problems that suggest I
> should change professions from statistician to Java developer -- not
> something I want to contemplate at this stage in my career.
>
>   Any advice for the harried and distraught _amateur_ programmer?
>
>   Thank you in advance!
>
>   -- Chris
>
>
>
>
>
> ----- Original Message -----
> From: Scott Palmer 
> To: Chris Olsen 
> Cc: users@netbeans.apache.org
> Sent: Tue, 24 Sep 2019 21:29:47 -0400 (EDT)
> Subject: Re: Hopefully close to the finish line with Java 11 & FX
>
> The target should be 11 not 1.11.
>
> Scott
>
> > On Sep 24, 2019, at 8:49 PM, Chris Olsen  wrote:
> >
> > Hello, Everyone --
> >
> >   I have downloaded AdoptOpenJDK, JavaFX 11, and Maven (or so I
> believe).  I have waded through getting to zero FX compile errors, and with
> the clarion call of "Excelcior!" I told Apache Netbeans 11.1 to run.  This
> is what I got:
> >
> > 
> > Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
> (default-compile) on project Splat_Maven: Fatal error compiling: error:
> invalid target release: 1.11 -> [Help 1]
> > 
> >
> >   I did my due diligence and looked for solutions on line, but nothing I
> found seemed to work.  What I'm thinking is that SOMEwhere I must have told
> some file or other that there is another Java 11 in town, but I don't
> really know where I would have said this.  (I blew away all my old Java 8
> JDKs.
> >
> >   In hopes that this might give someone might have greater than zero
> clues, I am appending some System output below.  Any ideas of what and
> where to look for solutions and/or suggestions for how to proceed are very
> welcome!  I'm running this on Windows 7, but my Windows 10 laptop gives the
> same "invalid target release" message.
> >
> >   Thanks in a

Re: Hopefully close to the finish line with Java 11 & FX

[Scott Palmer]

Javafxpackager was removed along with several other things in Java 11.  Sadly 
this was done with no reasonable path forward - there was no replacement for 
javapackager (it was renamed from javafxpackager because it isn’t strictly 
related to JavaFX), nor were many of the removed modules available with modular 
replacements (they were passed off to other open source communities to deal 
with, and those communities completely dropped the ball - Eclipse people I’m 
looking at you).


Anyway.. the new jpackage tool, that was originally intended for Java 13 and 
now is expected as an experimental feature of Java 14, is available as a 
pre-release and can be used to package an application with Java 11.

You can get the early-access build from here https://jdk.java.net/jpackage/ 
<https://jdk.java.net/jpackage/>

jpackage is a tool that will create a native installer for Windows, or a 
package for Linux or macOS, or just an application image.  It includes your 
application and the JRE required to run it, all nicely bundled together so it 
appears as any other platform-specific application.

The new jpackage tool serves the same purpose as javafxpackager, but it is not 
compatible.  The options have changed.

It may be an adventure getting your project working.  I’ve been there… the 
transition away from Java 8 has been a massive headache for this and a few 
other reasons.

Regards,

Scott


> On Sep 27, 2019, at 8:02 AM, Chris Olsen  wrote:
> 
> Scott and All --
> 
>> The target should be 11 not 1.11. 
> 
>  Thanks to Scott!  I'm not sure where the 1.11 came from -- I think it was 
> generated somewhere out of my control.  (Yes, passing the buck.)
> 
>  In any case, one step forward has gotten me to another problem, which I 
> believe is with something called javafxpackager:
> 
> ---
>  Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
> (unpack-dependencies) on project Splat_Maven: Command execution failed. 
> Cannot run program "C:\Program 
> Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\..\bin\javafxpackager" (in directory 
> "C:\Users\olsenc\Documents\NetBeansProjects\Splat_Maven"): CreateProcess 
> error=2, The system cannot find the file specified -> [Help 1]
> ---
> 
>  In searching the web I found a great deal of only partially helpful 
> information, much related to Java 6 and 7.  Some places, in discussing Java 
> 11, seemed to suggest there was no longer in existence a javafxpackager, and 
> would there not be one until Java 14.  This is distressing, as my app is 
> replete with FX.  I wonder if someone could give me an authoritative answer 
> about what javafxpackager -- if it exists -- actually does.  I believe would 
> like to be able to deploy my app bundled with Java 11 in Windows and Mac 
> versions because of my target audience (high school teachers with even less 
> computer savvy that I have).  I'm beginning to think I should just return to 
> Java 8. I have solved many problems in migrating to Java 11, but I am getting 
> a bit discouraged when I contemplate the possibility of many problems still 
> to come, problems that suggest I should change professions from statistician 
> to Java developer -- not something I want to contemplate at this stage in my 
> career.
> 
>  Any advice for the harried and distraught _amateur_ programmer?
> 
>  Thank you in advance!
> 
>  -- Chris
> 
> 
> 
> 
> 
> ----- Original Message -----
> From: Scott Palmer 
> To: Chris Olsen 
> Cc: users@netbeans.apache.org
> Sent: Tue, 24 Sep 2019 21:29:47 -0400 (EDT)
> Subject: Re: Hopefully close to the finish line with Java 11 & FX
> 
> The target should be 11 not 1.11. 
> 
> Scott
> 
>> On Sep 24, 2019, at 8:49 PM, Chris Olsen  wrote:
>> 
>> Hello, Everyone --
>> 
>>  I have downloaded AdoptOpenJDK, JavaFX 11, and Maven (or so I believe).  I 
>> have waded through getting to zero FX compile errors, and with the clarion 
>> call of "Excelcior!" I told Apache Netbeans 11.1 to run.  This is what I got:
>> 
>> 
>> Failed to execute goal 
>> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
>> on project Splat_Maven: Fatal error compiling: error: invalid target 
>> release: 1.11 -> [Help 1] 
>> 
>> 
>>  I did my due diligence and looked for solutions on line, but nothing I 
>> found seemed to work.  What I'm thinking is that SOMEwhere I must have told 
>> some file or other that there is another Java 11 in town, but I don't really 
>> know where I would have said this.  (I blew away all my old Java 8 JDKs.
>> 
>>  In hopes that this might give someone might have greater than zero clues,

Re: Hopefully close to the finish line with Java 11 & FX

[Chris Olsen]

Scott and All --

  > The target should be 11 not 1.11. 

  Thanks to Scott!  I'm not sure where the 1.11 came from -- I think it was 
generated somewhere out of my control.  (Yes, passing the buck.)

  In any case, one step forward has gotten me to another problem, which I 
believe is with something called javafxpackager:

---
  Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
(unpack-dependencies) on project Splat_Maven: Command execution failed. Cannot 
run program "C:\Program 
Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\..\bin\javafxpackager" (in directory 
"C:\Users\olsenc\Documents\NetBeansProjects\Splat_Maven"): CreateProcess 
error=2, The system cannot find the file specified -> [Help 1]
---

  In searching the web I found a great deal of only partially helpful 
information, much related to Java 6 and 7.  Some places, in discussing Java 11, 
seemed to suggest there was no longer in existence a javafxpackager, and would 
there not be one until Java 14.  This is distressing, as my app is replete with 
FX.  I wonder if someone could give me an authoritative answer about what 
javafxpackager -- if it exists -- actually does.  I believe would like to be 
able to deploy my app bundled with Java 11 in Windows and Mac versions because 
of my target audience (high school teachers with even less computer savvy that 
I have).  I'm beginning to think I should just return to Java 8. I have solved 
many problems in migrating to Java 11, but I am getting a bit discouraged when 
I contemplate the possibility of many problems still to come, problems that 
suggest I should change professions from statistician to Java developer -- not 
something I want to contemplate at this stage in my career.

  Any advice for the harried and distraught _amateur_ programmer?

  Thank you in advance!

  -- Chris





- Original Message -
From: Scott Palmer 
To: Chris Olsen 
Cc: users@netbeans.apache.org
Sent: Tue, 24 Sep 2019 21:29:47 -0400 (EDT)
Subject: Re: Hopefully close to the finish line with Java 11 & FX

The target should be 11 not 1.11. 

Scott

> On Sep 24, 2019, at 8:49 PM, Chris Olsen  wrote:
> 
> Hello, Everyone --
> 
>   I have downloaded AdoptOpenJDK, JavaFX 11, and Maven (or so I believe).  I 
> have waded through getting to zero FX compile errors, and with the clarion 
> call of "Excelcior!" I told Apache Netbeans 11.1 to run.  This is what I got:
> 
> 
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
> on project Splat_Maven: Fatal error compiling: error: invalid target release: 
> 1.11 -> [Help 1] 
> 
> 
>   I did my due diligence and looked for solutions on line, but nothing I 
> found seemed to work.  What I'm thinking is that SOMEwhere I must have told 
> some file or other that there is another Java 11 in town, but I don't really 
> know where I would have said this.  (I blew away all my old Java 8 JDKs.
> 
>   In hopes that this might give someone might have greater than zero clues, I 
> am appending some System output below.  Any ideas of what and where to look 
> for solutions and/or suggestions for how to proceed are very welcome!  I'm 
> running this on Windows 7, but my Windows 10 laptop gives the same "invalid 
> target release" message.
> 
>   Thanks in advance...
> 
>   -- Chris Olsen
> 
> 
> 
> Echo %JAVA_HOME%:
> 
> C:\Program Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\
> 
> Echo %MAVEN_HOME%:
> 
> c:\Program Files\Maven\apache-maven-3.6.2-bin\apache-maven-3.6.2\bin
> 
> 
> Path:
> 
> C:\Program 
> Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\bin;C:\ProgramData\Oracle\Java\javapath;C:\Program
>  Files 
> (x86)\CambridgeSoft\ChemOffice2015\ChemScript\Lib;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Anaconda3;C:\Anaconda3\Scripts;C:\Program
>  Files\MATLAB\R2015a\bin;c:\Program Files (x86)\Microsoft SQL 
> Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL 
> Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL 
> Server\100\DTS\Binn\;C:\PROGRAM FILES\OPENOFFICE.ORG 3\URE\BIN; C:\PROGRAM 
> FILES (X86)\OPENOFFICE.ORG 3\URE\BIN;C:\Program 
> Files\SASHome\Secure\ccme4;C:\Program 
> Files\SASHome\x86\Secure\ccme4;C:\Program Files (x86)\Skype\Phone\; 
> c:\Program Files (x86)\Inno Setup 5;C:\Program Files 
> (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\SMLNJ\bin\;%JAVA_HOME%\bin; 
> C:\Program Files\Java\jdk-11\bin;c:\Program 
> Files\Maven\apache-maven-3.6.2-bin\apache-maven-3.6.2\bin
> 
> -
> 
> -
>

Re: Hopefully close to the finish line with Java 11 & FX

[Scott Palmer]

The target should be 11 not 1.11. 

Scott

> On Sep 24, 2019, at 8:49 PM, Chris Olsen  wrote:
> 
> Hello, Everyone --
> 
>   I have downloaded AdoptOpenJDK, JavaFX 11, and Maven (or so I believe).  I 
> have waded through getting to zero FX compile errors, and with the clarion 
> call of "Excelcior!" I told Apache Netbeans 11.1 to run.  This is what I got:
> 
> 
> Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
> on project Splat_Maven: Fatal error compiling: error: invalid target release: 
> 1.11 -> [Help 1] 
> 
> 
>   I did my due diligence and looked for solutions on line, but nothing I 
> found seemed to work.  What I'm thinking is that SOMEwhere I must have told 
> some file or other that there is another Java 11 in town, but I don't really 
> know where I would have said this.  (I blew away all my old Java 8 JDKs.
> 
>   In hopes that this might give someone might have greater than zero clues, I 
> am appending some System output below.  Any ideas of what and where to look 
> for solutions and/or suggestions for how to proceed are very welcome!  I'm 
> running this on Windows 7, but my Windows 10 laptop gives the same "invalid 
> target release" message.
> 
>   Thanks in advance...
> 
>   -- Chris Olsen
> 
> 
> 
> Echo %JAVA_HOME%:
> 
> C:\Program Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\
> 
> Echo %MAVEN_HOME%:
> 
> c:\Program Files\Maven\apache-maven-3.6.2-bin\apache-maven-3.6.2\bin
> 
> 
> Path:
> 
> C:\Program 
> Files\AdoptOpenJDK\jdk-11.0.4.11-hotspot\bin;C:\ProgramData\Oracle\Java\javapath;C:\Program
>  Files 
> (x86)\CambridgeSoft\ChemOffice2015\ChemScript\Lib;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Anaconda3;C:\Anaconda3\Scripts;C:\Program
>  Files\MATLAB\R2015a\bin;c:\Program Files (x86)\Microsoft SQL 
> Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL 
> Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL 
> Server\100\DTS\Binn\;C:\PROGRAM FILES\OPENOFFICE.ORG 3\URE\BIN; C:\PROGRAM 
> FILES (X86)\OPENOFFICE.ORG 3\URE\BIN;C:\Program 
> Files\SASHome\Secure\ccme4;C:\Program 
> Files\SASHome\x86\Secure\ccme4;C:\Program Files (x86)\Skype\Phone\; 
> c:\Program Files (x86)\Inno Setup 5;C:\Program Files 
> (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\SMLNJ\bin\;%JAVA_HOME%\bin; 
> C:\Program Files\Java\jdk-11\bin;c:\Program 
> Files\Maven\apache-maven-3.6.2-bin\apache-maven-3.6.2\bin
> 
> -
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: users-h...@netbeans.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists