-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Relocation of the quarkus-vertx-web extension #20189
Conversation
…outes is a breaking change. This commit introduces a Maven relocation and so allows a smooth transition. Applications using the old artifact will get relocated automatically. A warning is displayed in the log indicating the relocation.
This comment has been minimized.
This comment has been minimized.
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.
Tested manually and it really works!
I will update the migration guide as well. |
This comment has been minimized.
This comment has been minimized.
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.
Awesome!
@glefloch any idea why so many (flaky?) Gradle errors in this PR? |
It's not this PR only: #20165 (comment) |
@gastaldi not they are not, it looks like gradle is not able to get plugins. There is an issue with bintray (which is used by the portal) this could come from that. |
I triggered the CI jobs again, let's see how that goes |
The renaming of the quarkus-vertx-web extension to quarkus-reactive-routes is a breaking change.
This PR introduces a Maven relocation and so allows a smooth transition. Applications using the old artifact will get relocated automatically. A warning is displayed in the log indicating the relocation.