Remove deprecated primitive wrapper constructor usage #8257

Activity

1. mbien

   added

   Code cleanupLabel for cleanup done on the Netbeans IDELabel for cleanup done on the Netbeans IDE

   Upgrade JDKUpgrade to the JDK requirements of a module.Upgrade to the JDK requirements of a module.

   on Feb 18, 2025
2. mbien

   added a parent issue on Feb 18, 2025

   • Technical debt reduction (compatibility with future JDKs) #8256
3. mbien

   added

   Java[ci] enable extra Java tests (java.completion, java.source.base, java.hints, refactoring.java, form)[ci] enable extra Java tests (java.completion, java.source.base, java.hints, refactoring.java, form)

   on Feb 18, 2025
4. mbien

   added a sub-issue on Feb 18, 2025

   • The GUI Builder produces code for boxed primitive properties that is deprecated for removal #7049
5. mbien commented on Sep 9, 2025

   

   mbien

   on Sep 9, 2025

   MemberAuthor

   More actions

   this might no longer be a priority:
   https://bugs.openjdk.org/browse/JDK-8354335

   although even if the constructors would remain the object identity would be likely still gone, so the refactoring to valueOf() was likely still a useful step.

   👍React with 👍1Reacted by Neil C Smith
6. neilcsmith-net commented on Sep 9, 2025

   

   neilcsmith-net

   on Sep 9, 2025

   Member

   More actions

   Absolutely still a useful step, and probably just as much a priority IMO. Making sure we handle all the cases where we have behaviour that relies on object identity is still really important. This helps ensure we've done that. I'm not sure I like the plan for new not to mean new - it muddies the water too much.
7. neilcsmith-net

   closed this as completedin #8799on Nov 3, 2025