Closed ivarmont closed 10 months ago
It is unclear to me why going from 4.0.3 to 4.0.1 fixes this.
It is unclear to me why going from 4.0.3 to 4.0.1 fixes this.
jaxb-runtime:4.0.3 (direct dependency) depends on jaxb-core:4.0.3 which requires jakarta.activation-api 2.1.2 and jakarta.xml.bind-api:4.0.0 jakarta.xml.bind-api:4.0.0 (direct dependency) requires jakarta.activation-api 2.1.0
So until the issue in jaxb-core is resolved the conflic can only be solved by downgrading jaxb-runtime to 4.0.1
Some dependencies are updated targeting these issues: