Re: NB and JDK 17 - OpenJDK Quality Outreach

Looks like I did not. Everything seems to work again once nb-javac is uninstalled. Many thanks Jan! On 7/25/21 12:06 AM, Jan Lahoda wrote: Do you have an up-to-date build of NetBeans? This has been fixed by this commit some time ago: https://github.com/apache/netbeans/commit/43338016d661b743

Re: NB and JDK 17 - OpenJDK Quality Outreach

Do you have an up-to-date build of NetBeans? This has been fixed by this commit some time ago: https://github.com/apache/netbeans/commit/43338016d661b74317892298d88b0a32663adb05 Jan On Sun, Jul 25, 2021 at 6:40 AM Ty Young wrote: > Thanks for verifying. > > > Netbeans is even more borked withou

Re: NB and JDK 17 - OpenJDK Quality Outreach

Thanks for verifying. Netbeans is even more borked without nb-javac for me. On load, all the projects that were open are closed except for the parent pom objects. Attempting to right click on a file under "Projects" on the left side does nothing. Files under "Projects" are still marked with e

Re: NB and JDK 17 - OpenJDK Quality Outreach

Hi Ty, Sorry, I missed this e-mail. I just tried a build from the current NetBeans master and Panama's foreign-memaccess+abi branch, using a simple Maven project. I can see the problem, but only with nb-javac installed. Given nb-javac is based on the last released JDK (i.e. JDK 16) and Panama is J

Re: NB and JDK 17 - OpenJDK Quality Outreach

Were* *sigh* On 7/24/21 9:08 PM, Ty Young wrote: Where you able to reproduce it by any chance? On 7/13/21 10:18 AM, Ty Young wrote: You may need to build from this branch, which I use: https://github.com/openjdk/panama-foreign/tree/foreign-memaccess+abi The default branch "foreign-jextra

Re: NB and JDK 17 - OpenJDK Quality Outreach

Where you able to reproduce it by any chance? On 7/13/21 10:18 AM, Ty Young wrote: You may need to build from this branch, which I use: https://github.com/openjdk/panama-foreign/tree/foreign-memaccess+abi The default branch "foreign-jextract" is based on foreign-memaccess+abi and is update

Re: Export/Import Options files is currently broken

Great! I will test it right away. Thanks. El sáb, 24 de jul. de 2021 a la(s) 21:22, Matthias Bläsing ( mblaes...@doppel-helix.eu) escribió: > Hi José, > > the isse was introduced by this PR: > > https://github.com/apache/netbeans/pull/3038 > > the problem is, that the displayName property refer

Re: Export/Import Options files is currently broken

Hi José, the isse was introduced by this PR: https://github.com/apache/netbeans/pull/3038 the problem is, that the displayName property references a missing bundle key, as the new key is in a different Bundle. With assertions enabled you get a sensible error message: INFO [org.netbeans.core.sta

Export/Import Options files is currently broken

Hi everyone, The Export/Import Options action is currently broken in master, I tried to export and import and the behavior is the same, never finished loading, can not continue and an exception is thrown. I could identified the culprit: [PR-3058] Micronaut: Allow for creating project on JDK 16

Re: Compiling NetBeans 12.5 with JDK 11

Some of these type of depreciation/removal concerns were why I raised the below ticket. I thought as impacted APIs a features were identified they could be linked to the story. NETBEANS-5349 Update Netbeans Codebase to Account for deprecated/removed API in Java 11/15 I had already identified a