Re: debug maven javafx app

[Geertjan Wielenga]

Great, thanks for that help Joe Schmo. :-) Specifically this from there:

https://github.com/zimmi/netbeans-non-modular-javafx-example/blob/master/nbactions.xml

Gj

On Thu, May 9, 2019 at 7:55 PM joe schmo  wrote:

> I don't know how to forward a previous message as an attachment, however,
> Thomas Zimmermann has provided this example which worked for me.
>
> https://github.com/zimmi/netbeans-non-modular-javafx-example
> 
> zimmi/netbeans-non-modular-javafx-example
> 
> Sample Maven project that integrates with default "Run" and "Debug"
> actions in NetBeans - zimmi/netbeans-non-modular-javafx-example
> github.com
>
>
>
> BC
> --
> *From:* John Brice 
> *Sent:* May 9, 2019 1:07 PM
> *To:* users@netbeans.apache.org
> *Subject:* debug maven javafx app
>
>
> How do I configure the Debug action for a Maven JavaFX project? Using
> NB11, JDK12 & OpenJFX 12.0.1 and the instructions at
> https://openjfx.io/openjfx-docs/#IDE-NetBeans I can edit, compile and run
> but I can’t figure out what to put in nbactions.xml to make debug work.
>
>
>
> I’ve been using exec-maven-plugin with JDK11 (couldn’t debug with that
> either) but should probably be using javafx-maven-plugin now, if possible.
>
>
>
> John
>
>
>

Re: debug maven javafx app

[joe schmo]

I don't know how to forward a previous message as an attachment, however, 
Thomas Zimmermann has provided this example which worked for me.

https://github.com/zimmi/netbeans-non-modular-javafx-example
[https://avatars2.githubusercontent.com/u/1998530?s=400=4]

zimmi/netbeans-non-modular-javafx-example
Sample Maven project that integrates with default "Run" and "Debug" actions in 
NetBeans - zimmi/netbeans-non-modular-javafx-example
github.com




BC

From: John Brice 
Sent: May 9, 2019 1:07 PM
To: users@netbeans.apache.org
Subject: debug maven javafx app


How do I configure the Debug action for a Maven JavaFX project? Using NB11, 
JDK12 & OpenJFX 12.0.1 and the instructions at 
https://openjfx.io/openjfx-docs/#IDE-NetBeans I can edit, compile and run but I 
can’t figure out what to put in nbactions.xml to make debug work.



I’ve been using exec-maven-plugin with JDK11 (couldn’t debug with that either) 
but should probably be using javafx-maven-plugin now, if possible.



John

debug maven javafx app

[John Brice]

How do I configure the Debug action for a Maven JavaFX project? Using NB11, 
JDK12 & OpenJFX 12.0.1 and the instructions at 
https://openjfx.io/openjfx-docs/#IDE-NetBeans I can edit, compile and run but I 
can’t figure out what to put in nbactions.xml to make debug work.

I’ve been using exec-maven-plugin with JDK11 (couldn’t debug with that either) 
but should probably be using javafx-maven-plugin now, if possible.

John

RE: Trouble patching NetBeans 11.0 platform module

[Joseph Huber]

Arsi wrote:
> I see no reason to compile the entire ANB when you need to change one class:

I am not compiling the entire ANB.  That’s the whole point of the “orphaned 
modules” FAQ.  You just pick out the modules you want to work on.  The ant 
“bootstrap” command is just building a few things necessary to facilitate that 
process.

To me, it seems that http://wiki.netbeans.org/DevFaqOrphanedNetBeansOrgModules 
is essentially doing what you have outlined below.

Thank You!

Joe Huber
Standard Refrigeration LLC
2005 Reverchon Dr
Arlington, TX  76017
Cell: 682-777-8374
jhu...@stanref.com

From: arsi 
Sent: Thursday, May 9, 2019 3:09 AM
To: users@netbeans.apache.org
Cc: Joseph Huber 
Subject: Re: Trouble patching NetBeans 11.0 platform module

Hi,

I see no reason to compile the entire ANB when you need to change one class:


Java Hacker's guide ;)



Jar is a plain zip file and nothing prevents us from replacing any class with 
our version.
Assuming that we preserve the original definition of methods and Inheritances.
We can change the body of methods without any problem.
Of course, you can also add a new method and additionally implement any 
interface in classpath.

If the patched library is available as maven artifact create a maven project 
and add that library as a dependency.
Otherwise, we will use the Ant project and we manually add that library and 
necessary dependencies.
Be sure to set the correct Java target level in the project..
Now we will create a package and a class that we want to patch.
After making the necessary adjustments, we will compile the project.
And in the ../target/classes directory, our patched classes are waiting for us.



You can find the Maven project with your patch here:
https://github.com/arsi-apli/ModulePatchExample



Now we just have to add / overwrite the original classes with ours in the jar.

Download the ANB 11 distribution zip and unpack it somewhere. Goto 
./netbeans/platform/modules/ and add the generated classes to 
org-netbeans-modules-autoupdate-ui.jar to correct package/folder




If you are developing the NB modules via ant, just add that unpacked ANB dist 
directory as the NB platform.
For maven it is necessary to modify original maven artifact jar file and  
publish this jar as new maven artifact version (locally) and use it as 
dependency.
And when you pack that unpacked distribution directory, you have a patched 
distribution..



I used this procedure to port Android tools libraries to support java > 8 in 
NBANDROID...




ArSi

From: Joseph Huber 
Sent: Wednesday, May 08, 2019 11:56PM
To: Arsi , Users 

Subject: RE: Trouble patching NetBeans 11.0 platform module
Hello!

I have a solution that works quite well in Netbeans 8.2. I believe that the 
question is whether or not this approach should still work with NetBeans 11.0.  
If it should, then I would like to find out why it isn’t working.  If the 
approach described at http://wiki.netbeans.org/DevFaqOrphanedNetBeansOrgModules 
is no longer valid for NetBeans 11.0, then so be it, and I will move to a 
different approach.

In the bigger picture, it would probably be helpful for others in the community 
using the method in the aforementioned FAQ to know whether the method is still 
valid for 11.0.

I don’t know if my platform patch is useful for others.  There didn’t seem to 
be much interest when it was being discussed on forums.netbeans.org back in 
2016.

Thank You!

Joe Huber
Standard Refrigeration LLC
2005 Reverchon Dr
Arlington, TX  76017
Cell: 682-777-8374
jhu...@stanref.com

From: arsi 
Sent: Wednesday, May 8, 2019 4:47 PM
To: users@netbeans.apache.org
Subject: Re: Trouble patching NetBeans 11.0 platform module

Hi,

If you only want a private patch, you can do a patch module:

http://wiki.netbeans.org/DevFaqModulePatching

Maven example:
https://github.com/NBANDROIDTEAM/org-netbeans-modules-masterfs-patches


ArSi

From: Joseph Huber 
Sent: Wednesday, May 08, 2019 11:30PM
To: Geertjan Wielenga 
Cc: Users 
Subject: RE: Trouble patching NetBeans 11.0 platform module
My patch is described here:
http://netbeans-org.1045718.n5.nabble.com/Update-Center-issue-How-to-hide-remove-items-from-the-Available-Plugins-tab-td5749157.html#a5749162

As for patching the zip, I am familiar with that process, and I am not familiar 
with the GitHub/pull request process.   Patching the zip previously worked fine.

Thank You!

Joe Huber
Standard Refrigeration LLC
2005 Reverchon Dr
Arlington, TX  76017
Cell: 682-777-8374
jhu...@stanref.com

From: Geertjan Wielenga 
Sent: Wednesday, May 8, 2019 4:03 PM
To: Joseph Huber 
Cc: 

Default JDK naming

[Luff,Chris]

Afternoon everyone; only nit, but in the Java Platforms the JDK that loaded 
NetBeans is labeled JDK 12 (Default) - where is that string obtained from? I 
would much rather it obtained its name from the actual version in my case; 
OpenJDK 12 as is done in the About NetBeans dialog.

If it cannot be changed locally, can anyone give me a starting point so I can 
make a change.

Thanks
C




CONFIDENTIALITY NOTICE This message and any included attachments are from 
Cerner Corporation and are intended only for the addressee. The information 
contained in this message is confidential and may constitute inside or 
non-public information under international, federal, or state securities laws. 
Unauthorized forwarding, printing, copying, distribution, or use of such 
information is strictly prohibited and may be unlawful. If you are not the 
addressee, please promptly delete this message and notify the sender of the 
delivery error by e-mail or you may call Cerner's corporate offices in Kansas 
City, Missouri, U.S.A at (+1) (816)221-1024. Cerner Limited, Registered in 
England no 2519305, Registered Office 37 North Wharf Road, London W2 1AF.

-
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

RE: Trouble patching NetBeans 11.0 platform module

[Joseph Huber]

Hello!

The problem is solved!  The error was on my part.  In NB 8.2, the “javahelp” 
folder is in the root (i.e. nb_all) of the source files.  However, in NB11.0, 
the javahelp folder has been moved into the “platform” folder.  When I was 
setting up the files for the build, I dragged the “javahelp” folder to the root 
again.  To correct, I just had to create a “platform” folder, and put the 
“javahelp” folder into the “platform” folder.   The bootstrap build completes 
without error.

Thank You!

Joe Huber
Standard Refrigeration LLC

From: Geertjan Wielenga 
Sent: Wednesday, May 8, 2019 10:07 PM
To: Emilian Bold 
Cc: Joseph Huber ; users@netbeans.apache.org
Subject: Re: Trouble patching NetBeans 11.0 platform module

But the build should succeed anyway, i.e., I don't see JavaHelp absence 
blocking the build from succeeding for me. So, I'd advise to try the build 
again and if it fails post the error message here. The build should succeed 
with later JDKs, but safest is to use JDK 8.

Gj

On Thu, May 9, 2019 at 1:00 AM Emilian Bold 
mailto:emilian.b...@gmail.com>> wrote:
JavaHelp was removed from Apache NetBeans due to an Apache licensing policy.

It's on my todo list for re-inclusion in CoolBeans (as some older
Platform apps use it).

--emi

On Wed, May 8, 2019 at 11:34 PM Joseph Huber 
mailto:jhu...@stanref.com>> wrote:
>
> Hello!
>
>
>
> I am in the initial phase of trying to patch a NetBeans 11.0 platform module 
> (which I have successfully done in NetBeans 8.2) per the procedure at 
> http://wiki.netbeans.org/DevFaqOrphanedNetBeansOrgModules.  I downloaded the 
> 11.0 source from the links at
>
> https://www.apache.org/dyn/closer.cgi/incubator/netbeans/incubating-netbeans/incubating-11.0/incubating-netbeans-11.0-source.zip
>
>
>
> The process is crashing at the “ant -f nbbuild/build.xml bootstrap” step with 
> numerous errors regarding javax.help, such as:
>
> nb_all\nbbuild\antsrc\org\netbeans\nbbuild\CheckHelpSets.java:37: error: 
> package javax.help does not exist
>
>
>
> In the netbeans 8.2 platform source, javahelp\external contains the following 
> files: binaries-list, jhall-2.0_05.jar, jhall-2.0_05-license.txt
>
>
>
> In the netbeans 11.0 platform source, javahelp\external contains the 
> following files:  binaries-list,  jhall-2.0_05-license.txt
>
>
>
> jhall-2.0_05.jar is missing in 11.0, which I believe is the source of the 
> above error.  The 11.0 binaries-list file contains the following text:
>
>
>
> # Licensed to the Apache Software Foundation (ASF) under one
>
> # or more contributor license agreements.  See the NOTICE file
>
> # distributed with this work for additional information
>
> # regarding copyright ownership.  The ASF licenses this file
>
> # to you under the Apache License, Version 2.0 (the
>
> # "License"); you may not use this file except in compliance
>
> # with the License.  You may obtain a copy of the License at
>
> #
>
> #   http://www.apache.org/licenses/LICENSE-2.0
>
> #
>
> # Unless required by applicable law or agreed to in writing,
>
> # software distributed under the License is distributed on an
>
> # "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
>
> # KIND, either express or implied.  See the License for the
>
> # specific language governing permissions and limitations
>
> # under the License.
>
> CA70822C47A67FC3A11670270567C2D01566DAE1 jhall-2.0_05.jar
>
>
>
> It seems that jhall-2.0_05.jar should be in the 11.0, javahelp\external 
> folder (like it is in 8.2), but it is missing.  Is this a bug?  I searched 
> through the 11.0 source, and I don’t find jhall-2.0_05.jar included.
>
> Thank You for any help!
>
>
>
> Joe Huber
>
> Standard Refrigeration LLC
>
> 2005 Reverchon Dr
>
> Arlington, TX  76017
>
> Cell: 682-777-8374
>
> jhu...@stanref.co

-
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

RE: [EXT] Re: duplicate project netbeans error, how coud I do it?

[Thomson, Duncan]

I don’t know what it means for a project to have “external source roots”, but 
as others have noted, you have other (better) ways of making a backup of your 
code rather than using the Netbeans function to copy a project.

Let me elaborate slightly.

One way to do this is to use your operating system, outside of netbeans, to 
copy the directory structure.  I would recommend first exiting netbeans, just 
to make sure everything is actually written out to disk.  Then navigate to the 
directory containing the project and copy the entire directory structure.

For example, on a Linux system your project might be 
/home/luistuti/NetBeansProjects/MostExcellentProject

Then you would use something like:
   $ cp  –archive  MostExcellentProject  MostExcellentProject-copy

Or create a tarball, using something like:
  $ tar -cvzf MostExcellentProject.tgz MostExcellentProject

But a much better way is to use a source code configuration control tool.  
Nowadays everyone is using git, and it’s really powerful, so unless you already 
have a favorite that you want to use, I suggest you get on board with git.  
Netbeans has very good integration with git, so you can do it from within 
Netbeans, or you can just go to the command line and run git commands from 
there.

Good luck!

Duncan

From: Luis tuti 
Sent: Monday, May 6, 2019 6:36 AM
To: Emilian Bold 
Cc: Geertjan Wielenga ; NetBeans Mailing 

Subject: [EXT] Re: duplicate project netbeans error, how coud I do it?

Yes, that's it.

El lun., 6 may. 2019 a las 10:08, Emilian Bold 
(mailto:emilian.b...@gmail.com>>) escribió:
Maybe this is the copy action from NetBeans?
--emi

lun., 6 mai 2019, 10:48 Geertjan Wielenga 
mailto:geert...@apache.org>> a scris:
You don't need NetBeans to copy a project, you can just go to your file system 
and copy it there.

Gj

On Mon, May 6, 2019 at 8:30 AM Luis tuti 
mailto:mierdat...@gmail.com>> wrote:

Hi, I'm trying to copy a project to have a backup and mofiy my copy but I get: 
"The project has one more external source roots and cannot be copied"

Someone could help me?

Thanks

RE: [EXT] Re: duplicate project netbeans error, how coud I do it?

[Thomson, Duncan]

I think the ability to copy projects within NetBeans is valuable, and should 
not be removed.  I use it, not for making backups, but for creating a new 
project in which I want to reuse some existing code or other stuff from an 
existing project.

Duncan

From: Emilian Bold 
Sent: Monday, May 6, 2019 1:27 PM
To: Thomson, Duncan 
Cc: Luis tuti ; Geertjan Wielenga ; 
NetBeans Mailing 
Subject: Re: [EXT] Re: duplicate project netbeans error, how coud I do it?

I think Luis figured out how to copy that folder but the question is why can't 
NetBeans figure that out?

Our copy action could be disabled if there is something that we don't support 
anyhow.

Or, we could get rid of the copy action entirely.

The problem is one of NetBeans UX.
--emi

lun., 6 mai 2019, 19:21 Thomson, Duncan 
mailto:dunc...@mitre.org>> a scris:
I don’t know what it means for a project to have “external source roots”, but 
as others have noted, you have other (better) ways of making a backup of your 
code rather than using the Netbeans function to copy a project.

Let me elaborate slightly.

One way to do this is to use your operating system, outside of netbeans, to 
copy the directory structure.  I would recommend first exiting netbeans, just 
to make sure everything is actually written out to disk.  Then navigate to the 
directory containing the project and copy the entire directory structure.

For example, on a Linux system your project might be 
/home/luistuti/NetBeansProjects/MostExcellentProject

Then you would use something like:
   $ cp  –archive  MostExcellentProject  MostExcellentProject-copy

Or create a tarball, using something like:
  $ tar -cvzf MostExcellentProject.tgz MostExcellentProject

But a much better way is to use a source code configuration control tool.  
Nowadays everyone is using git, and it’s really powerful, so unless you already 
have a favorite that you want to use, I suggest you get on board with git.  
Netbeans has very good integration with git, so you can do it from within 
Netbeans, or you can just go to the command line and run git commands from 
there.

Good luck!

Duncan

From: Luis tuti mailto:mierdat...@gmail.com>>
Sent: Monday, May 6, 2019 6:36 AM
To: Emilian Bold mailto:emilian.b...@gmail.com>>
Cc: Geertjan Wielenga mailto:geert...@apache.org>>; 
NetBeans Mailing mailto:users@netbeans.apache.org>>
Subject: [EXT] Re: duplicate project netbeans error, how coud I do it?

Yes, that's it.

El lun., 6 may. 2019 a las 10:08, Emilian Bold 
(mailto:emilian.b...@gmail.com>>) escribió:
Maybe this is the copy action from NetBeans?
--emi

lun., 6 mai 2019, 10:48 Geertjan Wielenga 
mailto:geert...@apache.org>> a scris:
You don't need NetBeans to copy a project, you can just go to your file system 
and copy it there.

Gj

On Mon, May 6, 2019 at 8:30 AM Luis tuti 
mailto:mierdat...@gmail.com>> wrote:

Hi, I'm trying to copy a project to have a backup and mofiy my copy but I get: 
"The project has one more external source roots and cannot be copied"

Someone could help me?

Thanks

Re: Trouble patching NetBeans 11.0 platform module

[arsi]

Hi,

I see no reason to compile the entire ANB when you need to change one class:

Java Hacker's guide ;)

Jar is a plain zip file and nothing prevents us from replacing any class 
with our version.
Assuming that we preserve the original definition of methods and 
Inheritances.

We can change the body of methods without any problem.
Of course, you can also add a new method and additionally implement any 
interface in classpath.


If the patched library is available as maven artifact create a maven 
project and add that library as a dependency.
Otherwise, we will use the Ant project and we manually add that library 
and necessary dependencies.

Be sure to set the correct Java target level in the project..
Now we will create a package and a class that we want to patch.
After making the necessary adjustments, we will compile the project.
And in the ../target/classes directory, our patched classes are waiting 
for us.



You can find the Maven project with your patch here:
https://github.com/arsi-apli/ModulePatchExample


Now we just have to add / overwrite the original classes with ours in 
the jar.


Download the ANB 11 distribution zip and unpack it somewhere. Goto 
./netbeans/platform/modules/ and add the generated classes to 
org-netbeans-modules-autoupdate-ui.jar to correct package/folder



If you are developing the NB modules via ant, just add that unpacked ANB 
dist directory as the NB platform.
For maven it is necessary to modify original maven artifact jar file 
and  publish this jar as new maven artifact version (locally) and use it 
as dependency.
And when you pack that unpacked distribution directory, you have a 
patched distribution..



I used this procedure to port Android tools libraries to support java > 
8 in NBANDROID...



ArSi

*From:* Joseph Huber 
*Sent:* Wednesday, May 08, 2019 11:56PM
*To:* Arsi , Users 
*Subject:* RE: Trouble patching NetBeans 11.0 platform module


Hello!

I have a solution that works quite well in Netbeans 8.2. I believe 
that the question is whether or not this approach should still work 
with NetBeans 11.0.  If it should, then I would like to find out why 
it isn’t working.  If the approach described at 
http://wiki.netbeans.org/DevFaqOrphanedNetBeansOrgModules is no longer 
valid for NetBeans 11.0, then so be it, and I will move to a different 
approach.


In the bigger picture, it would probably be helpful for others in the 
community using the method in the aforementioned FAQ to know whether 
the method is still valid for 11.0.


I don’t know if my platform patch is useful for others.  There didn’t 
seem to be much interest when it was being discussed on 
forums.netbeans.org back in 2016.


Thank You!

Joe Huber

Standard Refrigeration LLC

2005 Reverchon Dr

Arlington, TX  76017

Cell: 682-777-8374

jhu...@stanref.com

*From:*arsi 
*Sent:* Wednesday, May 8, 2019 4:47 PM
*To:* users@netbeans.apache.org
*Subject:* Re: Trouble patching NetBeans 11.0 platform module

Hi,

If you only want a private patch, you can do a patch module:

http://wiki.netbeans.org/DevFaqModulePatching

Maven example:

https://github.com/NBANDROIDTEAM/org-netbeans-modules-masterfs-patches

ArSi



*From:* Joseph Huber  
*Sent:* Wednesday, May 08, 2019 11:30PM
*To:* Geertjan Wielenga  
*Cc:* Users  
*Subject:* RE: Trouble patching NetBeans 11.0 platform module

My patch is described here:


http://netbeans-org.1045718.n5.nabble.com/Update-Center-issue-How-to-hide-remove-items-from-the-Available-Plugins-tab-td5749157.html#a5749162

As for patching the zip, I am familiar with that process, and I am
not familiar with the GitHub/pull request process.   Patching the
zip previously worked fine.

Thank You!

Joe Huber

Standard Refrigeration LLC

2005 Reverchon Dr

Arlington, TX  76017

Cell: 682-777-8374

jhu...@stanref.com 

*From:*Geertjan Wielenga 

*Sent:* Wednesday, May 8, 2019 4:03 PM
*To:* Joseph Huber  
*Cc:* users@netbeans.apache.org 
*Subject:* Re: Trouble patching NetBeans 11.0 platform module

I believe they should be downloaded during the build process.

But rather than patching via the ZIP, why not clone the GitHub
repo and then provide a pull request there?

What does your patch do?

Gj

On Wed, 8 May 2019 at 22:34, Joseph Huber mailto:jhu...@stanref.com>> wrote:

Hello!

I am in the initial phase of trying to patch a NetBeans 11.0
platform module (which I have successfully done in NetBeans
8.2) per the procedure at
http://wiki.netbeans.org/DevFaqOrphanedNetBeansOrgModules.  I
downloaded the 

Re: Question on Netbeans 11 and C++

[Geertjan Wielenga]

Well, you can use Java EE 8, right now, today. Just use a Maven archetype
that has the POM configured correctly, e.g., look for the AirHacks
archetypes by Adam Bien, search for them in the Maven project from
Archetype wizard in the New Project dialog.

At the same time, Josh Juneau is working on tweaking several modules
related to Java EE support specifically for Java EE 8, please join the
Apache NetBeans dev mailing list, he’d be very happy to hear of your
interest and feedback and requirements (now is the time to hear what they
are, not after he pushes his changes).

Note too that the Payara team plans to contribute support for Payara to
Apache NetBeans in time for the next release, scheduled for June.

Also be aware of the ongoing discussions re Java EE and Jakarta EE and the
Eclipse Foundation, etc. Too complex to summarize here, best if you do a
search for that on-line.

Thanks,

Gj


On Thu, 9 May 2019 at 07:41, Richard Grin 
wrote:

> When is Java EE *8* scheduled ? I cannot see it in the link.
>
> Thanks
>
> Richard
>
>
>
> Envoyé depuis mon smartphone Samsung Galaxy.
>
>
>  Message d'origine 
> De : Geertjan Wielenga 
> Date : 09/05/2019 05:07 (GMT+01:00)
> À : Emilian Bold 
> Cc : Koos du Preez , NetBeans Mailing <
> users@netbeans.apache.org>
> Objet : Re: Question on Netbeans 11 and C++
>
> Here's the roadmap, C/C++ inclusion is scheduled for September:
>
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+Roadmap
>
> Thanks,
>
> Gj
>
> On Thu, May 9, 2019 at 12:56 AM Emilian Bold 
> wrote:
>
>> > 1 Does NB11 also include C++ projects (I only saw Java, PHP and couple
>> other web based types)
>>
>> No. I suspect the next release will include the C++ projects.
>>
>> In the meantime you can try CoolBeans ( https://coolbeans.xyz ) which
>> does compile the C++ modules.
>>
>> > 3 Does NB11 support C++17 ?
>>
>> I suspect not entirely... but only because a low level library I know
>> related to the clang frontend is from Oct 2017 while C++17 seems to
>> have been finalized in 2018.
>>
>> Would be interested about your feedback.
>>
>> --emi
>>
>> On Wed, May 8, 2019 at 10:22 PM Koos du Preez
>>  wrote:
>> >
>> > We are using Netbeans 8.2 extensively for cross platform C++
>> development and I was curious with Netbeans 11 release, I have the
>> following questions
>> >
>> > 1 Does NB11 also include C++ projects (I only saw Java, PHP and couple
>> other web based types)
>> >
>> > 2 Can you upgrade NB8.2 projects to NB11 ?
>> >
>> > 3 Does NB11 support C++17 ?
>> >
>> >
>> > Thanks!
>>
>> -
>> 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
>>
>>

Re: How to test a NetBeans Platform app? NbTestCase classpath woes

[Emilian Bold]

Indeed, the java.class.path is much larger for tests.

--emi

On Fri, Apr 26, 2019 at 10:24 PM Emilian Bold  wrote:
>
> One trick I learned is that .clusters() is applied only to the cluster
> folder name, not the full path.
>
> This was kinda obvious really, but since the current suite has the
> cluster under build/cluster I assumed it might be the full path. But
> no, your regexp has to also match 'cluster'.
>
> This doesn't solve the classpath problem mentioned initially...
>
> --emi
>
> On Thu, Apr 25, 2019 at 11:16 AM Emilian Bold  wrote:
> >
> > Hello,
> >
> > I'm trying to introduce NbTestCase into a large existing app and I'm
> > getting all kinds of what seem to be class-loader/classpath problems.
> >
> > The whole NbModuleSuite.Configuration is quite limited in what it does
> > and I can't seem to find any combination of settings that starts the
> > application properly.
> >
> > The code uses some libraries that read "JAI (Java Advanced Imaging)
> > registry files" inside META-INF/registryFile.jai and also some
> > java.util.ServiceLoader.
> >
> > It seems that no matter how I run the configuration:
> > * with hand-picked clusters or just .clusters(".*") or
> > * with hand-picked enableModules or just ".*" or
> > * enableClasspathModules(false)
> >
> > ... I get some duplicated entries in the classpath.
> >
> > Then I get a warning like:
> >
> > > Error while parsing JAI registry file 
> > > "file:/home/nasa/DSCOVR/SecretLunarBase/release/modules/ext/some.jar"
> >
> > But that release/modules/ext folder is *not* supposed to be in the
> > classpath as I already have the same JAR in the suite build/cluster/
> > folder (which folder is shown at app startup under `Installation=`).
> >
> > So, is there a way to configure NbTestCase so 'it just works'? I don't
> > want any fewer modules, I just want the application to start normally,
> > then execute
> > my test, without breaking the classpath in ways that are
> > test-specific.
> >
> > Regards,
> >
> >
> > --emi

-
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

RE: Java 9+ is the module-info wizard too rigorous?

[Alten, Jessica-Aileen]

I don't know. I will have to build Netbeans and understand how Netbeans works, 
where the unit tests are, etc. I've never done that before.  I've also just 
started working with the Java module system!

The bug is documented in JIRA: 
https://issues.apache.org/jira/browse/NETBEANS-2519



Kind regards,

Jessica

From: Geertjan Wielenga 
Sent: Thursday, May 9, 2019 5:40 AM
To: Alten, Jessica-Aileen 
Cc: users@netbeans.apache.org
Subject: Re: Java 9+ is the module-info wizard too rigorous?



Thanks a lot for this great analysis and welcome to the NetBeans community.



I think the main problem here is that I don't think there's anyone who is very 
knowledgeable about this part of the code.



Do you expect that a lot of code will need to be changed to fix this or is 
this a simple change or tweak that's needed somewhere specific?



Thanks,



Gj



On Mon, May 6, 2019 at 2:13 PM Alten, Jessica-Aileen 
mailto:jessica-aileen.al...@leibniz-liag.de> > wrote:

Hi,

I am quite new to the JDK 9+ module system but I think I found a bug in the
Netbeans module-info wizard (only tested with Netbeans 11). The problem is
the code generation for automatic modules, which seems too rigorous. In my
case, it is a maven project, but that does not matter, the Netbeans build
mechanism produces the same result.

Example: Using the jdom2-2.0.6.jar leads to this code

module mymodulename {
requires jdom;
}

Netbeans is fine with this, no errors, code completion works, but compiling
the code gives a compilation error:
... module not found: jdom

Changing "requires jdom" to "requires jdom2", in module-info.java results in
lots of red error badges in module-info.java and other classes, code
completion does not work and import statement says, "package org.jdom2.input
is declared in module jdom, but module mymodulename does not read it."

 But this works! Compilation is ok and the the class using the jdom2 package
is working fine!

Calling "jar --describe-module --file=jdom2-2.0.6.jar" gives:

jdom2@2.0.6   automatic
requires java.base mandated
contains org.jdom2
contains org.jdom2.adapters
contains org.jdom2.filter
contains org.jdom2.input
contains org.jdom2.input.sax
contains org.jdom2.input.stax
contains org.jdom2.internal
contains org.jdom2.located
contains org.jdom2.output
contains org.jdom2.output.support
contains org.jdom2.transform
contains org.jdom2.util
contains org.jdom2.xpath
contains org.jdom2.xpath.jaxen
contains org.jdom2.xpath.util

I read some articles about the module mechanism of JDK 9+ especially about
automatic modules and know that name generation for automatic modules
truncates the version string part, in this case that would be "-2.0.6" but
not "2-2.0.6", "2" is a distinctive feature not a version string. I think
the Netbeans wizard is doing too much here. Would you confirm this?

I know about the workarounds, i.e. modifying META-INF/MANIFEST.MF in the jar
file and I know that this library should be updated for JDK 9+, but I think
Netbeans should behave like the --describe-module result.
Or did I misunderstand something fundamentally?

Kind regards,
Jessica






smime.p7s
Description: S/MIME cryptographic signature