I'm aware the sky is blue and water is wet, thanks. You had said that
JDK 17 was being worked on. Clearly that was a lie. What's the point of
forcing people to join a dev list just so you tell them this?
Netbeans has never technically supported in-dev builds but they've
always generally worked. What's going on here?
On 7/11/21 12:18 AM, Geertjan Wielenga wrote:
Indeed, NetBeans does not support JDK 18 (also not JDK 17) at this stage.
Gj
On Sun, 11 Jul 2021 at 04:12, Ty Young <[email protected]> wrote:
>
Hi,
I use JDK 18 builds of Project Panama[1] that Netbeans does not work
properly with. All classes with JDK 18 have errors with the package
statement claiming that:
Cannot access java.lang
Fatal Error: Unable to find package java.lang in classpath or
bootclasspath.
This happens even on the "dev" builds of Netbeans[2]. My JavaFX
application and all dependency projects compile and run fine. Code
completion and import suggestions are broken, Netbeans views some
imports as unused when they are being used, and symbols(classes) are
marked as "cannot be found" even though they have imports.
[1] https://github.com/openjdk/panama-foreign. Technically PR source
here: https://github.com/mcimadamore/panama-foreign/tree/handle_address
[2] https://ci-builds.apache.org/job/Netbeans/job/netbeans-linux/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
