On Wed, Apr 10, 2024 at 6:27 PM Basil Crow <m...@basilcrow.com> wrote:
> Even if we did want to migrate core and plugins to […] a different JSON > library […], we'd have to continue to support JSON-lib under the net.sf > package namespace during the transition period at the very least. > I think it is worse than that, because jsonlib types are exposed in core API signatures. For example https://issues.jenkins.io/browse/JENKINS-67344 cannot be solved merely by switching to a reasonable parser, since you would still need to provide compatibility for https://javadoc.jenkins.io/hudson/model/UpdateSite.html#getJSONObject() and similar. So in the short term, being able to deliver patches to jsonlib would be helpful. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3D%2B7ZmhxR7eBSfr5UfTsJ8F50KfZBvup7g4cUCtpsS_Q%40mail.gmail.com.
