You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "onobc (via GitHub)" <gi...@apache.org> on 2023/03/21 13:40:50 UTC

[GitHub] [pulsar] onobc commented on issue #19856: Update jaxb and jax-rs libs

onobc commented on issue #19856:
URL: https://github.com/apache/pulsar/issues/19856#issuecomment-1477858374

   
   Hi @nodece ,
   
   >1. Migrate to jakarta.* from javax.* in the admin@3.0.0
   
   Agreed. This is what I was referring to in the **Solution** section. 
   
   > BUMP jakarta.ws.rs:jakarta.ws.rs-api from 2.1.6 to 3.1.0
   > BUMP jakarta.xml.bind:jakarta.xml.bind-api from 2.3.3 4.0.0
   > Remove javax.xml.bind:jaxb-api:2.3.1
   > 
   > Update all code references from javax.* to jakarta.*
   
   And 3.0.0 sounds like the proper vehicle for that significant change.
   
   >2. Could you try to use the pulsar-client-admin-shaded in your project?
   
   I am using `pulsar-client-all` which has the same effect.
   
   On a positive note, I believe `2.11` did increase these libs being shaded (from `2.10.x`). The only one that is not shaded is the ` javax.xml.bind:jaxb-api:2.3.1`. 
   
   I would be satisfied w/ making the upgrade (and move to `jakarta.*`) in `3.0.0` and I can live w/ the `2.11.0` containing `javax` for now. It mostly triggering "prohibited classpath compatibility" checks on some apps. 
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org