-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Should use Oracle Maven repository to obtain Oracle JDBC driver #73
Comments
Yes that would be great, but the oracle repository requires you to authorize yourself with your oracle account. It's not possible to have a private maven config where you can securely store this credentials on Circle CI I think. Do you have an idea on how to solve this? Reference: Get Oracle JDBC drivers and UCP from Oracle Maven Repository |
Ah crap, I'd seen the other announcement but not groked the detail about needing to still use credentials. CircleCI's environment variables can technically be used to get credentials into the build, but to be secure you have to disable builds of PRs (in case they modify the build to steal the credentials). This isn't something I'd want to do. Oh well, maybe something to come back to one day, but seems pretty improbable :( |
The time has come.... :) https://medium.com/@kuassimensah/oracle-jdbc-drivers-on-maven-central-64fcf724d8b |
Thanks for re-opening 😀 Contributions would be welcomed! |
This is undoubtedly great news. BUT I'm afraid I have to crash this party again somehow: It turned out that Oracle doesn't tolerate public Oracle docker images and sends DMCA Takedown Notices. I was using wnameless/docker-oracle-xe-11g which was removed from Docker Hub because of this in the past. This issue sums it up: jhipster/generator-jhipster#9370. I'm going to contribute a small change to the oracle-xe module to use an official JDBC driver but |
Also removed two unnecessary dependencies.
fixed in #1899 |
Now that the Oracle JDBC driver is available in a public repository, the
oracle-xe
module can be part of the CI build and there is no need for the proprietary-deps profile.The text was updated successfully, but these errors were encountered: