-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Make reactive-oracle-client depend on jdbc-oracle #25624
Conversation
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.
LGTM, let's see what the CI says.
The test failures looks unrelated:
|
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.
I don't think it's wise to pull in the JDBC quarkus extension as a dependency as that will trigger transitive dependencies which are necessary to setup a JDBC pool, and trigger other build items related to JDBC use of Oracle - which we likely want to skip in this case.
Could you extract a common module for the stuff you need to reuse? Or actually I'm not even sure if there's much in common, you most likely want to reuse some of the native-image support rules but they are most likely going to be needing different tuning.
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 meant to suggest making some changes.
Fixes quarkusio#25415 Reactive Oracle Client extension does not work in native mode. Instead of duplicating code, this commit makes the reactive client extension depend on jdbc client extension.
This comment has been minimized.
This comment has been minimized.
When there are multiple candidates for the same kind (i.e. reactive + jdbc), an implicit db kind can be chosen instead of returning an empty optional.
Failing Jobs - Building 56ebc43
Full information is available in the Build summary check run. Failures⚙️ JVM Tests - JDK 11 Windows #- Failing: extensions/vertx/deployment
! Skipped: extensions/agroal/deployment extensions/amazon-lambda-http/deployment extensions/amazon-lambda-rest/deployment and 334 more 📦 extensions/vertx/deployment✖
|
@Sanne @cescoffier since we've come to an agreement about this PR, can we go ahead and merge it? The single CI failure is unrelated. |
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.
Ok - sorry for the delay, have been travelling.
thanks @tsegismont ! |
Fixes #25415
Reactive Oracle Client extension does not work in native mode.
Instead of duplicating code, this PR makes the reactive client extension depend on jdbc client extension.
Also, it enables Reactive Oracle Client integration tests in native mode.