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 Camel 3.3.0 #1224
Upgrade to Camel 3.3.0 #1224
Conversation
@jamesnetherton @lburgazzoli would you mind throwing a final look? |
I have manually cancelled the push workflow |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks ok to me. I left one question about version overrides.
We should bump & align spring.version
too.
<dependency> | ||
<groupId>org.mongodb</groupId> | ||
<artifactId>bson</artifactId> | ||
<version>${mongodb.version}</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just curious - how do these overrides work out in the Quarkus Universe BOM?
Do we end up overriding their Mongo version? Or does their version take precedence again?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point I should have documented my intention. Actually the main problem is that Quarkus does not manage bson
. That causes conflicts on our side because camel-mongodb pulls a different version transitively. Best would be to let Quarkus manage bson
too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd improve it in a followup if you do not mind.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Filed quarkusio/quarkus#9330
LGTM |
Let me do it in a followup. |
No description provided.