On 01.03.24 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.
what Java distribution is this you tried to add? if its the one from the
link you posted it would be a JRE I believe. Oracle has a separate
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,
Thank you for your input.
8-21 you say? But i tried Java 8 too and it gave the same error.
I am confused about all these versions. How come if you download the
latest JRE from Oracle you get Java 8 since the JDK went all the way up
to 21?
On 01/03/2024 16:15, Michael Bien wrote:
NetBeans 21
Hi,
I have old java sources, which I want to work on with NetBeans 21.
Location of the existing sources is:
~/Projects/Palm/NetbeansProjects/DesktopFiles_src/
Location for the new project is:
~/Projects/Palm/NetbeansProjects/DesktopFiles/
So these are separate paths, but I get:
! Project
Am 01.03.24 um 15:24 schrieb Michael Bien:
NetBeans ships with nb-javac preinstalled as regular module, if you don't
change anything it should just work. Start NB, open/create a project and the
right modules will activate.
You want to say, that I do not have to activate "Java SE" plugin
Am 01.03.24 um 15:24 schrieb Michael Bien:
there are several red flags here which might cause you problems in future:
- Don't start NB with root rights. Subsequent starts will likely not be able
to write to cache/log folders.
I used `sudo -H` to avoid this.
- The "force plugin install
Am 01.03.24 um 15:51 schrieb Neil C Smith:
You can replicate running with a clean userdir by running
netbeans --userdir /tmp/testuserdir1
Thanks for the hint.
Sorry, should have been clearer - I meant NetBeans packaging. Between
ASF and community options there's zip, deb (x2), appimage and
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
On Fri, 1 Mar 2024 at 14:44, Ulf Zibis wrote:
> 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.
>
> This I assumed too, so I'm wondering about my ecperience.
So am I! If you can find
Am 01.03.24 um 15:25 schrieb Neil C Smith:
The above two steps might have been what fixed it. Have you been
using NetBeans for a while and copying forward configuration and
plugins?
No, I didn't import old configuration and I deleted ~/.cache/netbeans and
~/.netbeans/21
nb-javac is
On 01.03.24 14:43, Ulf Zibis wrote:
Am 29.02.24 um 22:12 schrieb Geertjan Wielenga:
The Apache NetBeans 21 binary releases require JDK 11+, and
officially supports running on JDK 11, 17 and 21.
Thanks for the info.
In the meantime I solved the problem still using JDK 18 as follows.
-
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
Am 29.02.24 um 22:12 schrieb Geertjan Wielenga:
The Apache NetBeans 21 binary releases require JDK 11+, and officially supports
running on JDK 11, 17 and 21.
Thanks for the info.
In the meantime I solved the problem still using JDK 18 as follows.
- deleted user config data and reinstalled
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
Brother, you're working for the wrong company. Adding fake/senseless
tests decreases the quality of the software. As a developer you are not
allowed to do that.
Testing the data layer against the database is the right thing to do
here and you can do it in an integration test and also use
15 matches
Mail list logo
