-
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
Oracle JDBC drivers should not be initialized at runtime #23178
Conversation
I could not find this fix on the 2.7 branch. Maybe you will backport it later? |
@bvahdat yes, gsmet has a script that alignes the branches in batches. The label "backport" marks it for the script to take it later. If you want to try it out, feel free to cherry-pick it.. should be trivial. |
(or wait a day.. :) ) |
Awesome, I prefer to wait then 👍 |
@Sanne at my end I wanted to try out your fix, but I still get the same error. Do you maybe know what I'm doing wrong? I cloned https://github.com/quarkusio/quarkus And did
Maybe not necessary, but I also did:
Then cloned https://github.com/quarkusio/quarkus-platform and did:
As the last step I changed the version to
|
If you want a quick test, just change the groupId of the BOM and Maven plugin from If you want to test with the Platform, make sure you have updated the Quarkus version in the Platform parent pom. The |
@Sanne native build works great now, thanks for fixing that. Now at runtime with native mode I am running into the next problem. Do you maybe have an idea what the problem could be? |
Fixes #23113
Tested locally; this would need a module with both JDBC drivers from Oracle and DB2 - not sure what we want to do there, so let's discuss it separately and try to have the fix in 2.7 (as I'm unlikely to be able to contribute the integration test by then).