It's probably not the RIGHT way to do it, but it does work. What I did instead was to include the jar in my project (blech) and then create a "system" dependency for it that indicates the path to the jar. If your team has a local Maven repository this guide might be helpful to upload the JAR there.įor whatever reason, I could not get any of the above solutions to work. The last parameter for generating a POM will save you from pom.xml warnings Dversion=10.2.0.3.0 -Dpackaging=jar -Dfile=ojdbc.jar -DgeneratePom=true Once you've downloaded the JAR just add it to your computer repository with (note I pulled the groupId, artifactId and version from the POM): mvn install:install-file -DgroupId=com.oracle -DartifactId=ojdbc14 \ and the URL to download the file which in this case is Just check it out, it contains the vendor's preferred Maven info: com.oracle Some JARs that can't be added due to license reasons have a pom entry in the Maven Central repo. How do I add it so that Maven will use it? If you happen to find a public repository containing the JAR you can be sure that is illegal. This happens with many dependencies but is not Maven's fault. Unfortunately due the binary license there is no public repository with the Oracle Driver JAR. How do I find a repository (if any) that contains this artifact?
0 kommentar(er)
