Great advice, thanks. Gj
On Sat, 28 Sep 2019 at 22:21, William Reynolds < wnreyno...@stellarscience.com> wrote: > TL;DR - edit your system path, and remove the jdk1.8 from it. Make sure > your jdk11 is first. > > The problem is that the javafx maven plugin is trying to execute the java > that is first on your PATH variable. You have both a JDK 11 and a JDK 8, > the JDK 8 is first on your path. The maven-compiler-plugin is (correctly) > looking at your java platform and using that to compile things, but the > javafx maven plugin is incorrectly using your path (I don't see an option > to configure the jdk you use for the javafx plugin, it seems to ignore > JAVA_HOME). Anyways, fix your path and things will work. > > > On 9/28/2019 1:53 PM, Geertjan Wielenga wrote: > > Possibly, but unless we can reproduce this or get a better understanding > of the environment in question, we won't know. > > Gj > > On Sat, Sep 28, 2019 at 9:51 PM Neil C Smith <neilcsm...@apache.org> > wrote: > >> >> >> On Sat, 28 Sep 2019, 20:31 Geertjan Wielenga, <geert...@apache.org> >> wrote: >> >>> Yup, it seems to me that the Java environment isn't set up right -- some >>> JDK 8 of some kind appears to be set up system wide. >>> >> >> Yes, but shouldn't cause an issue should it? The Maven support should set >> up the environment for the build platform? Just wondering whether it might >> be the sign of a bug in NetBeans or the Gluon projects. >> >> Neil >> >>> > -- > William Reynolds, Ph.D. > Stellar Science, llcwnreyno...@stellarscience.comwww.stellarscience.com > 877-763-8268 x710 (v) > >
