Modify

#22432 closed defect (fixed)

[PATCH] Start migrating from javax to jakarta

Reported by: taylor.smock Owned by: team
Priority: normal Milestone: 23.05
Component: Core Version:
Keywords: Cc:

Description

In core, we use javax.json. This is often used in turn by downstream plugins, so we should keep the javax dependency until sometime next year.

Attachments (1)

22432.patch (30.3 KB ) - added by taylor.smock 19 months ago.

Download all attachments as: .zip

Change History (5)

by taylor.smock, 19 months ago

Attachment: 22432.patch added

comment:1 by taylor.smock, 19 months ago

Summary: Start migrating from javax to jakarta[PATCH] Start migrating from javax to jakarta

comment:2 by taylor.smock, 13 months ago

Milestone: 23.04

comment:3 by taylor.smock, 12 months ago

Milestone: 23.0423.05

Ticket retargeted after milestone closed

comment:4 by taylor.smock, 12 months ago

Resolution: fixed
Status: newclosed

In 18723/josm:

Fix #22432, see #22941: Start migrating from javax to jakarta

Parsson was split out from the JSONP repository in 2021 (see
https://github.com/jakartaee/jsonp-api/issues/285 ). It is the default provider,
and will "just work" without additional configuration.

Many plugins use javax.json, so the scheduled removal of the javax.json
dependencies is set to milestone:"24.12" (see #22941).

Changes between javax.json and jakarta.json 2.0:

  • Rename of javax.json to jakarta.json
  • Some additional bug fixes

This will enable us to move easily to jakarta.json 2.1 in the future.
The changes of note with 2.1 includes:

  • Better handling of duplicated keys
  • Additional APIs around primitive types
  • API to get current event from JsonParser

We cannot currently move to jakarta.json 2.1 since it requires Java 11+.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.