Make XChange compatible with jakarta.ws.rs-api 3.x

[ppalaga]

As far as I can see, the jakarta.ws.rs-api is pulled transitively via com.github.mmazi:rescu. Once a com.github.mmazi:rescu release compatible with jakarta.ws.rs-api 3.x is available, XChange should be adjusted as well. This is currently blocked by mmazi/rescu#142

It would be nice to have this to be able to use XChange on Quarkus 3.x.

[ppalaga]

mmazi/rescu#142 was fixed and com.github.mmazi:rescu 3.0 was released.

[martinformi]

I would be also quite interested in having this. It prevents me now to use Spring Boot 3.x. Unfortunately, how other projects are solving this is a bit not comfortable - having two libraries released, one with jakarta.* another one with javax.*, since it is breaking change.

[martinformi]

@ppalaga Peter, use this if needed - https://github.com/martinformi/XChange/tree/feature/jakarta-namespace

[ppalaga]

@ppalaga Peter, use this if needed - https://github.com/martinformi/XChange/tree/feature/jakarta-namespace

Great, would you mind sending a pull request against https://github.com/knowm/XChange ?

[martinformi]

I do not think the PR would be approved anytime soon, it is a breaking change that would break any usage in javax.* environments. That would mean having two different artifacts - xchange and xchange-jakarta. I will create PR and let's see.

Created PR - #4710.

[ppalaga]

Thanks for the PR. It is up to the project maintainers to decide how they deal with the incompatibility. I'd personally be fine with bumping the major version as having both xchange and xchange-jakarta dependencies in one project would not work anyway - it would not be possible to have transitives compatible with both of them.

[bigscoop]

@ppalaga looks like the MR #4735 resolves it. Feel free to test and eventually close the issue

[ppalaga]

Thanks for the heads up @bigscoop!

[jdlee726]

is already fixed?

[bigscoop]

yes, issue can be closed