Hi Geertjan,
While reading your reply I think it is better that we closed our
conversation. Your answers are not much of a help. And it certainly has
nothing to do with not being able to make choices!
I am exploring all the possibilities of Netbeans11.0 with java12/javafx12.
In my environment some ways work others don't. That's why I am also looking
into the modular way of working, and why not!
Never mind, I will not address you anymore and leave it up to the community.
Regards.
Op do 6 jun. 2019 om 14:16 schreef Geertjan Wielenga :
> The key problem is that you need to make a choice: are you using Ant or
> Maven? Are you creating a modular application or not?
>
> No one can help you if in each and every mail you send you're trying
> something completely different -- i.e., now you suddenly mention
> module-info.java, which means you're creating a modular application.
>
> What is it that you want to achieve? No one can help you, if you don't
> know.
>
> Gj
>
> On Thu, Jun 6, 2019 at 2:13 PM Eef Custers wrote:
>
>> Hi Jose,
>>
>> Thanks for your respons.
>>
>> This commandline was generated by Netbeans in case one did not wanted to
>> use Ant. This generated line contains errors ( colons instead of
>> semecolons), which I ofcourse removed. The rest of the config is collected
>> from internal settings. Indeed the mods directory is also configured in
>> Netbeans. In another programs I used the module-info.java. That build went
>> OK, but alo the run failed. I am really amased that these new versions do
>> not match. I am now almost two weeks going over the internet and trying all
>> kinds of ways of working, but I did not find a solution. Maybe the advise
>> will be: stay at version 8 for Java/JavaFX and Netbeans?
>>
>> Regards,
>>
>> Eef
>>
>>
>>
>>
>> Op do 6 jun. 2019 om 13:50 schreef jose.per...@gluonhq.com <
>> jose.per...@gluonhq.com>:
>>
>>> Hi Eef,
>>>
>>> Your command line says otherwise, but it tells what it is ultimately
>>> running:
>>>
>>> c:\java_lib\jdk-12.0.1/bin/java \
>>> -p C:\java_lib\javafx-jmods-12.0.1;
>>>C:\java_lib\javafx-jmods-12.0.1;
>>>
>>>
>>> C:\java_lib\javafx-sdk-12.0.1\lib\javafx-swt.jar;C:\java_lib\javafx-sdk-12.0.1\lib\javafx.base.jar;
>>> *C:\java_lib\javafx-sdk-12.0.1\lib\javafx.controls.jar;
>>> *C:\java_lib\javafx-sdk-12.0.1\lib\javafx.fxml.jar;... \
>>> -cp C:\java_lib\javafx-sdk-12.0.1\lib\javafx-swt.jar;
>>> C:\java_lib\javafx-sdk-12.0.1\lib\javafx.base.jar;
>>> *C:\java_lib\javafx-sdk-12.0.1\lib\javafx.controls.jar;...
>>> ;D:\NbProjects\FxApp01_c\dist\FxApp01_c.jar \
>>> fxapp01_c.FxApp01_c
>>>
>>> In this command line there are a few issues:
>>> - No "--add-modules javafx.controls,javafx.fxml"
>>> - JavaFX jmods and SDK mixed in the same module-path
>>> - Weird path " *C:\...", this looks bad.
>>>
>>> Please follow the sample:
>>> https://github.com/openjfx/samples/tree/master/IDE/NetBeans/Non-Modular/Java
>>>
>>> And make sure you have the right libraries and Path.
>>>
>>> Jose
>>>
>>> On 2019/06/06 11:36:17, Eef Custers wrote:
>>> > Hi Jose,
>>> >
>>> > I did not missed step 5, I had that configured. As you can read in my
>>> other
>>> > reply to Geertjan something is going wrong at the initialisation of the
>>> > boot layer. The VM parameters processing is complaining about the last
>>> > value in the list, no matter what the value is.
>>> >
>>> > Regards,
>>> > Eef
>>> >
>>> > Op do 6 jun. 2019 om 10:34 schreef jose.per...@gluonhq.com <
>>> > jose.per...@gluonhq.com>:
>>> >
>>> > > Hi, you can still use Ant, of course, but as Geertjan already
>>> pointed out,
>>> > > you are missing this:
>>> > >
>>> > > --add-modules javafx.fxml,javafx.controls
>>> > >
>>> > > (no need for javafx.base nor javafx.graphics, as these are transitive
>>> > > dependencies of javafx.controls).
>>> > >
>>> > > which is also shown in the pic
>>> > >
>>> https://openjfx.io/openjfx-docs/images/ide/netbeans/ide/netbeans07.png
>>> > > that is part of the mentioned tutorial (step 5 VM options).
>>> > >
>>> > > About your module-path, there is an issue too: you shouldn't mix
>>> > > javafx-jmods with javafx-sdk paths. Mods are only required to do a
>>> custom
>>> > > image from a modular project, which doesn't seem to be your case now.
>>> > >
>>> > > Jose
>>> > >
>>> > > On 2019/06/06 05:08:23, Geertjan Wielenga
>>> wrote:
>>> > > > Even without javafx.graphics there, it works.
>>> > > >
>>> > > > Gj
>>> > > >
>>> > > > On Thu, Jun 6, 2019 at 7:07 AM Geertjan Wielenga <
>>> geert...@apache.org>
>>> > > > wrote:
>>> > > >
>>> > > > > For me, it suddenly started working when I was following the
>>> > > instructions
>>> > > > > re --add-modules:
>>> > > > >
>>> > > > > --add-modules javafx.fxml,javafx.controls,javafx.graphics
>>> > > > >
>>> > > > > In the place indicated in the instructions, add the above.
>>> > > > >
>>> > > > > Gj
>>> > > > >
>>> > > > > On Thu, Jun 6, 2019 at 6:44 AM Geertjan Wielenga <
>>> geert...@apache.org>
>>> > > > > wrote:
>>> > > > >
>>> > > > >>
