Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

resolve dependency conflicts for jakarta.xml bind-api and activation-api #456

Merged
merged 1 commit into from
Oct 6, 2023

Conversation

ivarmont
Copy link
Contributor

@ivarmont ivarmont commented Oct 6, 2023

Some dependencies are updated targeting these issues:

@lookfirst
Copy link
Owner

It is unclear to me why going from 4.0.3 to 4.0.1 fixes this.

@ivarmont
Copy link
Contributor Author

ivarmont commented Oct 6, 2023

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

@lookfirst lookfirst merged commit faef489 into lookfirst:master Oct 6, 2023
@kelunik
Copy link

kelunik commented Oct 16, 2024

@lookfirst Could you tag a new release with this change, please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants