Re: Missing nb-javac plugin in NetBeans IDE 21

2024-03-02 Thread Michael Bien

On 01.03.24 17:42, Ulf Zibis wrote:


Am 01.03.24 um 15:24 schrieb Michael Bien:

  - The "force plugin install into shared directories" is not a good 
idea

Why is it provided?


For historic reasons and to solve some edge cases. I vaguely remember 
using this option for a native lib wrapper module in early days, since 
the JVM can load the same native lib only once without causing trouble. 
So by adding the module to the platform/IDE made sure that it was in 
front of the class path and it wasn't loaded twice. But today you would 
use other tricks to achieve something similar.


But its not there to encourage running NB with root rights.

I prefer to install binaries under binaries locations, which is 
/usr/lib here. /home is for data and configs. Helps to minimize backup 
footprint an allows all users to profit from the installed binaries.

(esp with root rights)
Under which conditions it is possible to install in shared directories 
without root rights?


e.g by launching nb from the platform independent zip.

but as mentioned before: nb-javac is part of NetBeans - it does not need 
to be installed since it is already there. A fresh NetBeans distribution 
with new user config not finding it would indicate some other issue, e.g 
corrupted installation or some problems with access rights etc - I don't 
know.


-mbien


-
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: Missing nb-javac plugin in NetBeans IDE 21

2024-03-02 Thread Arbol One

Yes!
Thank you, it is working perfectly now.

On 2024-03-01 9:25 a.m., Neil C Smith wrote:

On Fri, 1 Mar 2024 at 13:43, Ulf Zibis  wrote:

In the meantime I solved the problem still using JDK 18 as follows.

- deleted user config data and reinstalled NetBeans

...

- Restart. All is fine !!!

Don't know, if that is a good workaround.

The above two steps might have been what fixed it.  Have you been
using NetBeans for a while and copying forward configuration and
plugins?

nb-javac is included in NetBeans since NB13, so you should not see
this dialog unless you've deliberately disabled this support and run
on an older JDK.  If you see it again, please report an issue.

Also, include the package you're using - there are multiple options on
Ubuntu, which might have an effect on what's happening.

Best wishes,

Neil

-
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


--
*/ArbolOne.ca/* Using Fire Fox and Thunderbird. ArbolOne is composed of 
students and volunteers dedicated to providing free services to 
charitable organizations. ArbolOne on Java Development is in progress [ í ]

Re: Netbeans 22 does not allow JDK 1.7 or 1.8

2024-03-02 Thread Mark Eggers
Is there a minimum JDK 8 version that is required in order to be 
recognized by NetBeans?


That would be an interesting question to answer (and possibly document).

I know that there are some Maven plugins that have a minimum required 
JDK 8 version.


I wonder if the original author could go and download the latest JDK 8 
from an appropriate vendor and try that. If that solves the problem, 
then maybe the section that offers to download a JDK needs to be looked at.


I don't know, since I manage all of the Java versions on my platforms 
independently of NetBeans.


. . . . just my two cents
/mde/

On 3/2/2024 8:26 AM, Michael Bien wrote:
its possible that there is a bug somewhere. Btw the link you posted is 
for the download archive.


JDK 8 would be at u402. I have all JDKs (8-23) in the platform manager 
and they are all recognized by NB.


-mbien


On 02.03.24 09:12, Noel Abela wrote:
You can clearly see from the filename in the screen shot that it is 
not a jre but a JDK. I got it from the oracle site here


https://www.oracle.com/java/technologies/javase/javase8-archive-downloads.html

I guess it is a bug.

Thanks for the other tips

On 01/03/2024 22:56, Noel Abela wrote:

Thanks again for your input.

As you can see from the  attached screenshot I am getting the same 
error for Java 8. But thanks to your suggestion, I managed to install 
8 anyway by downloading it from within the platform manager itself.


As for the version issue, I am not sure if I am explaining myself 
well. Below is the link where one can install the latest version of 
Java which is 8. This is what the users of my application will do 
before running my application.


https://www.java.com/download/ie_manual.jsp

If I build my application with a higher JDK their java will not allow 
them to run my application. I would have to install their Java 
runtime myself. I was just looking into this jlink that you mentioned 
and I must say it looks interesting. What will have to be seen 
however, is the final size of the distribution package. This will 
obviously be larger than my present jar file and this will make 
updates more inefficient but to what degree is what needs to be seen. 
I will certainly try this out.


I will venture an answer to my own question of why java 8 is the 
latest jre available. Is it maybe because jlink started from JDK9? If 
so, then they are assuming that everyone will be using jlink which 
might not be the case.



On 01/03/2024 19:01, Michael Bien wrote:

On 01.03.24 18:24, Noel Abela wrote:
I am confused about all these versions. How come if you download 
the latest JRE from Oracle


this explains it. The platform manager expects a JDK, not a JRE. The 
concept of JRE is a bit dated and no longer well defined since the 
introduction of jlink, which allows to create your own JRE if needed.


I thought we added a better error msg in case a user tries to 
register a JRE - apparently not ;)




you get Java 8 since the JDK went all the way up to 21?


yeah. so here is the summary:

 - NetBeans 21 requires JDK 11, 17, or 21 to run as you can see on 
the download page.


 - You should be able to register JDK 8 or later using the java 
platform manager and use it for your projects.


 - 1.7 won't be possible anymore since the editor of NB relies on a 
recent version of javac (which is bundled with NB), and javac itself 
does no longer support the Java 7 target (8 works fine)



How come if you download the latest... 


The Platform Manager itself can download JDKs.

This community maintained website might also help to find a version 
from a vendor you prefer: https://javaalmanac.io/


If you install a JDK using tools like sdkman or a regular repository 
on linux, NB should automatically add it to the platform manager 
since it scans some well-known directories.


best regards,

-mbien



On 01/03/2024 16:15, Michael Bien wrote:
NetBeans 21 supports projects which use JDKs in the rage 8-21 with 
limited support for early access dev builds 22, 23 etc.


javac itself dropped support for the 1.7 target in Java 20.

So your best bet would be to try NetBeans 17 which used nb-javac 
based on JDK 19. Although I can't promise that this will work 
since I don't think anyone tested anything with Java 7 for quite 
some time.


-mbien

On 01.03.24 10:32, Noel Abela wrote:

I have just installed Nebeans 22 which is using JDK 21.
I need to maintain a desktop application which is on JDK 1.7 but 
when I attempt to add this JDK and even JDK 1.8, Netbeans gives 
the following error ...



"Cannot detect and install the selected platform. The Java or 
javac may not be executable."


I have read in other forums that this was a bug way back in 
version 10 or 11.
I would have imagined that this would have been solved by version 
22.

Does anyone know some fix or workaround for this?

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

Re: Netbeans 22 does not allow JDK 1.7 or 1.8

2024-03-02 Thread Michael Bien
its possible that there is a bug somewhere. Btw the link you posted is 
for the download archive.


JDK 8 would be at u402. I have all JDKs (8-23) in the platform manager 
and they are all recognized by NB.


-mbien


On 02.03.24 09:12, Noel Abela wrote:
You can clearly see from the filename in the screen shot that it is 
not a jre but a JDK. I got it from the oracle site here


https://www.oracle.com/java/technologies/javase/javase8-archive-downloads.html 



I guess it is a bug.

Thanks for the other tips

On 01/03/2024 22:56, Noel Abela wrote:

Thanks again for your input.

As you can see from the  attached screenshot I am getting the same 
error for Java 8. But thanks to your suggestion, I managed to install 
8 anyway by downloading it from within the platform manager itself.


As for the version issue, I am not sure if I am explaining myself 
well. Below is the link where one can install the latest version of 
Java which is 8. This is what the users of my application will do 
before running my application.


https://www.java.com/download/ie_manual.jsp

If I build my application with a higher JDK their java will not allow 
them to run my application. I would have to install their Java 
runtime myself. I was just looking into this jlink that you mentioned 
and I must say it looks interesting. What will have to be seen 
however, is the final size of the distribution package. This will 
obviously be larger than my present jar file and this will make 
updates more inefficient but to what degree is what needs to be seen. 
I will certainly try this out.


I will venture an answer to my own question of why java 8 is the 
latest jre available. Is it maybe because jlink started from JDK9? If 
so, then they are assuming that everyone will be using jlink which 
might not be the case.



On 01/03/2024 19:01, Michael Bien wrote:

On 01.03.24 18:24, Noel Abela wrote:
I am confused about all these versions. How come if you download 
the latest JRE from Oracle


this explains it. The platform manager expects a JDK, not a JRE. The 
concept of JRE is a bit dated and no longer well defined since the 
introduction of jlink, which allows to create your own JRE if needed.


I thought we added a better error msg in case a user tries to 
register a JRE - apparently not ;)




you get Java 8 since the JDK went all the way up to 21?


yeah. so here is the summary:

 - NetBeans 21 requires JDK 11, 17, or 21 to run as you can see on 
the download page.


 - You should be able to register JDK 8 or later using the java 
platform manager and use it for your projects.


 - 1.7 won't be possible anymore since the editor of NB relies on a 
recent version of javac (which is bundled with NB), and javac itself 
does no longer support the Java 7 target (8 works fine)



How come if you download the latest... 


The Platform Manager itself can download JDKs.

This community maintained website might also help to find a version 
from a vendor you prefer: https://javaalmanac.io/


If you install a JDK using tools like sdkman or a regular repository 
on linux, NB should automatically add it to the platform manager 
since it scans some well-known directories.


best regards,

-mbien



On 01/03/2024 16:15, Michael Bien wrote:
NetBeans 21 supports projects which use JDKs in the rage 8-21 with 
limited support for early access dev builds 22, 23 etc.


javac itself dropped support for the 1.7 target in Java 20.

So your best bet would be to try NetBeans 17 which used nb-javac 
based on JDK 19. Although I can't promise that this will work 
since I don't think anyone tested anything with Java 7 for quite 
some time.


-mbien

On 01.03.24 10:32, Noel Abela wrote:

I have just installed Nebeans 22 which is using JDK 21.
I need to maintain a desktop application which is on JDK 1.7 but 
when I attempt to add this JDK and even JDK 1.8, Netbeans gives 
the following error ...



"Cannot detect and install the selected platform. The Java or 
javac may not be executable."


I have read in other forums that this was a bug way back in 
version 10 or 11.
I would have imagined that this would have been solved by version 
22.

Does anyone know some fix or workaround for this?

- 


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



Javadoc - using MS-Edge

2024-03-02 Thread Arbol One

Hi there!

In my Debian 12, I use Netbeans 21 (funny revers versions, ja, ja, ja) 
as my IDE.


I'd like to use MS-Edge as the output browser for javadoc, for that I 
have added it to Tools > Options > General > Web Browser.

---

/Edge is not an option in the pull-down menu,so, I added it like this 
Web Browser > Name : Edge | Process: 
/opt/microsoft/msedge/microsoft-edge | Argument : -remote 
"openURL({URL})" | Argument Hint : {URL} = URL of the page to be loaded 
by the web browser

/

---

However, when Edge opens the url for the javadoc, it opens it with the 
following url address signature:


http://openurl(file/home/USER/Documents/NetbeansWorkSpace/JavaSE/Test/dist/javadoc/index.html)/
/

Thus, the page is not open saying "Hmmm… can't reach this page".

What did I do wrong? What can I do to get Edge to open the javadoc properly?


Thanks in advance.

--
*/ArbolOne.ca/* Using Fire Fox and Thunderbird. ArbolOne is composed of 
students and volunteers dedicated to providing free services to 
charitable organizations. ArbolOne on Java Development is in progress [ í ]

Re: Netbeans 22 does not allow JDK 1.7 or 1.8

2024-03-02 Thread Mark Eggers

I just installed NetBeans 21 running on JDK 17.

I have several old projects that build against JDK 8. I've added JDK 8 
to my installed Java Platforms, set my Properties->Build->Compile to the 
correct JDK (1.8), and have set source and target in the maven compiler 
plugin to 1.8.


The project loads and builds as expected.

If I could get everyone to move to our latest parent pom, I could avoid 
installing JDK 8, set the Java release version to 8, and have it built.


I have tested the latter, and it works as well. It's just a matter of 
getting everyone to switch.


. . . . just my two cents
/mde/

On 3/2/2024 12:12 AM, Noel Abela wrote:
You can clearly see from the filename in the screen shot that it is not 
a jre but a JDK. I got it from the oracle site here


https://www.oracle.com/java/technologies/javase/javase8-archive-downloads.html

I guess it is a bug.

Thanks for the other tips

On 01/03/2024 22:56, Noel Abela wrote:

Thanks again for your input.

As you can see from the  attached screenshot I am getting the same 
error for Java 8. But thanks to your suggestion, I managed to install 
8 anyway by downloading it from within the platform manager itself.


As for the version issue, I am not sure if I am explaining myself 
well. Below is the link where one can install the latest version of 
Java which is 8. This is what the users of my application will do 
before running my application.


https://www.java.com/download/ie_manual.jsp

If I build my application with a higher JDK their java will not allow 
them to run my application. I would have to install their Java runtime 
myself. I was just looking into this jlink that you mentioned and I 
must say it looks interesting. What will have to be seen however, is 
the final size of the distribution package. This will obviously be 
larger than my present jar file and this will make updates more 
inefficient but to what degree is what needs to be seen. I will 
certainly try this out.


I will venture an answer to my own question of why java 8 is the 
latest jre available. Is it maybe because jlink started from JDK9? If 
so, then they are assuming that everyone will be using jlink which 
might not be the case.



On 01/03/2024 19:01, Michael Bien wrote:

On 01.03.24 18:24, Noel Abela wrote:
I am confused about all these versions. How come if you download the 
latest JRE from Oracle


this explains it. The platform manager expects a JDK, not a JRE. The 
concept of JRE is a bit dated and no longer well defined since the 
introduction of jlink, which allows to create your own JRE if needed.


I thought we added a better error msg in case a user tries to 
register a JRE - apparently not ;)




you get Java 8 since the JDK went all the way up to 21?


yeah. so here is the summary:

 - NetBeans 21 requires JDK 11, 17, or 21 to run as you can see on 
the download page.


 - You should be able to register JDK 8 or later using the java 
platform manager and use it for your projects.


 - 1.7 won't be possible anymore since the editor of NB relies on a 
recent version of javac (which is bundled with NB), and javac itself 
does no longer support the Java 7 target (8 works fine)



How come if you download the latest... 


The Platform Manager itself can download JDKs.

This community maintained website might also help to find a version 
from a vendor you prefer: https://javaalmanac.io/


If you install a JDK using tools like sdkman or a regular repository 
on linux, NB should automatically add it to the platform manager 
since it scans some well-known directories.


best regards,

-mbien



On 01/03/2024 16:15, Michael Bien wrote:
NetBeans 21 supports projects which use JDKs in the rage 8-21 with 
limited support for early access dev builds 22, 23 etc.


javac itself dropped support for the 1.7 target in Java 20.

So your best bet would be to try NetBeans 17 which used nb-javac 
based on JDK 19. Although I can't promise that this will work since 
I don't think anyone tested anything with Java 7 for quite some time.


-mbien

On 01.03.24 10:32, Noel Abela wrote:

I have just installed Nebeans 22 which is using JDK 21.
I need to maintain a desktop application which is on JDK 1.7 but 
when I attempt to add this JDK and even JDK 1.8, Netbeans gives 
the following error ...



"Cannot detect and install the selected platform. The Java or 
javac may not be executable."


I have read in other forums that this was a bug way back in 
version 10 or 11.

I would have imagined that this would have been solved by version 22.
Does anyone know some fix or workaround for this?

-
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 

Re: Netbeans 22 does not allow JDK 1.7 or 1.8

2024-03-02 Thread Noel Abela
You can clearly see from the filename in the screen shot that it is not 
a jre but a JDK. I got it from the oracle site here


https://www.oracle.com/java/technologies/javase/javase8-archive-downloads.html

I guess it is a bug.

Thanks for the other tips

On 01/03/2024 22:56, Noel Abela wrote:

Thanks again for your input.

As you can see from the  attached screenshot I am getting the same 
error for Java 8. But thanks to your suggestion, I managed to install 
8 anyway by downloading it from within the platform manager itself.


As for the version issue, I am not sure if I am explaining myself 
well. Below is the link where one can install the latest version of 
Java which is 8. This is what the users of my application will do 
before running my application.


https://www.java.com/download/ie_manual.jsp

If I build my application with a higher JDK their java will not allow 
them to run my application. I would have to install their Java runtime 
myself. I was just looking into this jlink that you mentioned and I 
must say it looks interesting. What will have to be seen however, is 
the final size of the distribution package. This will obviously be 
larger than my present jar file and this will make updates more 
inefficient but to what degree is what needs to be seen. I will 
certainly try this out.


I will venture an answer to my own question of why java 8 is the 
latest jre available. Is it maybe because jlink started from JDK9? If 
so, then they are assuming that everyone will be using jlink which 
might not be the case.



On 01/03/2024 19:01, Michael Bien wrote:

On 01.03.24 18:24, Noel Abela wrote:
I am confused about all these versions. How come if you download the 
latest JRE from Oracle


this explains it. The platform manager expects a JDK, not a JRE. The 
concept of JRE is a bit dated and no longer well defined since the 
introduction of jlink, which allows to create your own JRE if needed.


I thought we added a better error msg in case a user tries to 
register a JRE - apparently not ;)




you get Java 8 since the JDK went all the way up to 21?


yeah. so here is the summary:

 - NetBeans 21 requires JDK 11, 17, or 21 to run as you can see on 
the download page.


 - You should be able to register JDK 8 or later using the java 
platform manager and use it for your projects.


 - 1.7 won't be possible anymore since the editor of NB relies on a 
recent version of javac (which is bundled with NB), and javac itself 
does no longer support the Java 7 target (8 works fine)



How come if you download the latest... 


The Platform Manager itself can download JDKs.

This community maintained website might also help to find a version 
from a vendor you prefer: https://javaalmanac.io/


If you install a JDK using tools like sdkman or a regular repository 
on linux, NB should automatically add it to the platform manager 
since it scans some well-known directories.


best regards,

-mbien



On 01/03/2024 16:15, Michael Bien wrote:
NetBeans 21 supports projects which use JDKs in the rage 8-21 with 
limited support for early access dev builds 22, 23 etc.


javac itself dropped support for the 1.7 target in Java 20.

So your best bet would be to try NetBeans 17 which used nb-javac 
based on JDK 19. Although I can't promise that this will work since 
I don't think anyone tested anything with Java 7 for quite some time.


-mbien

On 01.03.24 10:32, Noel Abela wrote:

I have just installed Nebeans 22 which is using JDK 21.
I need to maintain a desktop application which is on JDK 1.7 but 
when I attempt to add this JDK and even JDK 1.8, Netbeans gives 
the following error ...



"Cannot detect and install the selected platform. The Java or 
javac may not be executable."


I have read in other forums that this was a bug way back in 
version 10 or 11.

I would have imagined that this would have been solved by version 22.
Does anyone know some fix or workaround for this?

-
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