Deploying JARs where you don’t have the original source Sometimes you need to use a JAR, but it hasn’t been published to a Maven repository. This sometimes happens with database drivers, reporting tools, or other closed source dependencies. If you have been provided a JAR, and you want to be able to depend on it in your Maven based projects, you can deploy it to Deps. Configuring Maven settings Before you start, you need to install Maven.
How to configure your repository to allow or prevent overwriting deployed versions By default, once an artifact version has been deployed, users are not allowed to redeploy the same version over top of the existing one. Instead of redeploying a version, it is recommended that you always create a new version. Why is redeployment usually bad? Most of the time, you don’t want to allow redeploying versions, as this can lead to confusing situations and unreproducible builds.
The Oracle OJDBC JAR is a common dependency for anyone wanting to connect to an Oracle database from Java. Oracle has a Maven repository that you can add to download Oracle JDBC drivers and other Oracle JARs. However not all of Oracle’s JARs (notably including OJDBC6) are not available on their Maven repository.
Historically Java releases moved at a slow pace. Open source projects and companies could comfortably stay on the same version for several years. Recently the release cadence has quickened with Java’s new six-monthly release schedule. Starting with Java 9, a new version is released every six months. Now many applications and projects need to support a wide range of Java versions.
In the Java/Maven ecosystem there are many repositories that publish JARs publicly. This is an up-to-date list of the ones that you are likely to encounter.