As the core implementation is hard coded towards javax.json, Artemis requires using javax.json libraries as we use
However we have users that require jakarta APIs, and since our server implementation relies on javax.json, we would need to provide a shaded version of our server as well. And this is honestly getting out of hand. We already provide shaded client libraries.. but now users want the dependency switch optionally on the server's as well. Can't we refactor the core implementation to have public implementations without requiring javax.json or jakarta.json? and then having a facade on top of the implementation for each binding? -- Clebert Suconic
