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

Upgrade to Glassfish Jaxb 2.3.2 and deal with move to Jakarta API dependencies #15689

Closed
wilkinsona opened this issue Jan 11, 2019 · 2 comments
Closed
Labels
type: dependency-upgrade A dependency upgrade
Milestone

Comments

@wilkinsona
Copy link
Member

No description provided.

@wilkinsona wilkinsona added this to the 2.1.2 milestone Jan 11, 2019
@wilkinsona wilkinsona added the type: dependency-upgrade A dependency upgrade label Jan 11, 2019
@wilkinsona
Copy link
Member Author

wilkinsona commented Jan 11, 2019

This introduces quite a big change for a maintenance release that requires further consideration.

In 2.3.2, jaxb-runtime has switched from javax.xml.bind:jaxb-api to jakarta.xml.bind:jakarta.xml.bind-api. This in turn causes a switch from javax.activation:javax.activation-api to jakarta.activation:jakarta.activation-api. Due to other modules, such as hibernate-core, having a dependency on jaxb-api, switching to the new Jakarta modules will require exclusions to be configured otherwise we'll end up with two different copies of the same API on the classpath.

@wilkinsona wilkinsona reopened this Jan 11, 2019
@wilkinsona wilkinsona modified the milestones: 2.1.2, 2.1.x Jan 11, 2019
@wilkinsona wilkinsona added the for: team-attention An issue we'd like other members of the team to review label Jan 11, 2019
@wilkinsona wilkinsona changed the title Upgrade to Glassfish Jaxb 2.3.2 Upgrade to Glassfish Jaxb 2.3.2 and deal with move to Jakarta API dependencies Jan 11, 2019
wilkinsona added a commit that referenced this issue Jan 11, 2019
@wilkinsona wilkinsona removed the for: team-attention An issue we'd like other members of the team to review label Jan 23, 2019
@wilkinsona wilkinsona modified the milestones: 2.1.x, 2.2.x Jan 23, 2019
@wilkinsona
Copy link
Member Author

We've decided this is too disruptive for a 2.1.x release. We intend to defer this till 2.2.x where the level of disruption would be more reasonable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: dependency-upgrade A dependency upgrade
Projects
None yet
Development

No branches or pull requests

1 participant