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.

Sign up for GitHub

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

Jump to bottom

Upgrade org.gradlex.java-ecosystem-capabilities from 1.0 to 1.1 (review after v4/spring6) #7387

Closed
planetf1 opened this issue Feb 1, 2023 · 1 comment
Closed

Upgrade org.gradlex.java-ecosystem-capabilities from 1.0 to 1.1 (review after v4/spring6) #7387

planetf1 opened this issue Feb 1, 2023 · 1 comment
Assignees
@planetf1

Comments

@planetf1
Copy link
Member

planetf1 commented Feb 1, 2023

See #7345

The javax/jakarta ee functionality clashes are common as libraries are moved around/dependencies updated.
Thie one gets entangled with spring, so I recommend we defer until we've upgraded to version 4 of egeria, java 17, and spring

Raising this issue to track
@planetf1 planetf1 mentioned this issue Feb 1, 2023
Merged
@planetf1 planetf1 self-assigned this Feb 1, 2023
@planetf1
Copy link
Member Author

This change has been made as part of the v4 updates

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@planetf1 planetf1

Labels
None yet
Projects
No open projects
Egeria V4.0 Planning
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@planetf1