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 few (I believe nashorn was one such link) [NETBEANS-4168] Handling Nashorn Removal inline with JDK 15 Not sure much work is being done and if so, maybe done by others that I’m not aware of or on tickets not yet identified. To add to that, how should these sort of changes be introduced (for example with generics - as indicated never introduced early on and may add more work and risks when introduced)? Do you do it across the codebase or introducing it as new code comes onn? When introducing new java versions, assume this means the source/target and minimum required JDK would also have to be updates. Eric On Wed, Jul 14, 2021 at 5:34 PM Kenneth Fogel <[email protected]> wrote: > For my own amusement I tried to compile the NetBeans 12.5 beta using Java > 16 and 17 on my new Windows system. In both cases there was an issue with > not finding the JavaScript engine. JS support in Java was deprecated in > Java 11 but it was not removed until Java 15 This is not new information. I > assume a replacement is being determined > > The deprecation messages are more worrisome. Sure, much of Date was > deprecated probably 20 years ago but it is still around. JavaScript support > was deprecated in 11 and gone in 15 hence being unable to compile NB with > 16 or 17. Is there a 'deprecation' team that is tracking each of these 5128 > issues and a 'rawtypes' team cleaning up the generics issue? There may be > more issues lurking in the compiler output. > > I was happy to see that you can generate JDK 17 code out of NB 12.5 or so > it seems based on these initial tests. > > Ken > > > > > > > -- Eric Bresie [email protected]
