Trova driver JDBC Oracle nel repository Maven
https://stackoverflow.com/questions/1074869
italiano
english
français
española
中国
日本の
العربية
Deutsch
한국어
Português
RussianDomanda
Voglio aggiungere il driver JDBC Oracle per il mio progetto come (portata runtime) la dipendenza - ojdbc14. Nel sito MVNrepository la dipendenza di mettere in POM è:
<dependency>
<groupId>com.oracle</groupId>
<artifactId>ojdbc14</artifactId>
<version>10.2.0.3.0</version>
</dependency>
Naturalmente questo lavoro does't in quanto non è nel repository centrale usata da Maven. 2 domande:
-
Come faccio a trovare un repository (se presente) che contiene questo artefatto?
-
Come faccio ad aggiungere in modo che Maven lo userà?
Soluzione
Come faccio a trovare un repository (se presente) che contiene questo artefatto?
Purtroppo a causa della licenza binario non v'è alcun archivio pubblico con il driver Oracle JAR. Questo succede con molte dipendenze, ma non è colpa di Maven. Se vi capita di trovare un archivio pubblico che raccoglie le JAR si può essere sicuri che sia illegale.
Come si aggiunge in modo che Maven lo userà?
Alcuni vasi che non possono essere aggiunti a causa di motivi di licenza hanno una pom voce nel Maven repo centrale . Basta controllare fuori, contiene informazioni preferito Maven del fornitore:
<groupId>com.oracle</groupId>
<artifactId>ojdbc14</artifactId>
<version>10.2.0.3.0</version>
... e l'URL per scaricare il file che in questo caso è http://www.oracle.com/technology/software/tech /java/sqlj_jdbc/index.html .
Una volta scaricato il JAR è sufficiente aggiungere al vostro computer con repository (si noti Ho tirato la groupId, artifactId e versione dalla parte POM):
mvn install:install-file -DgroupId=com.oracle -DartifactId=ojdbc14 \
-Dversion=10.2.0.3.0 -Dpackaging=jar -Dfile=ojdbc.jar -DgeneratePom=true
L'ultimo parametro per la generazione di un POM vi salverà da avvertimenti pom.xml
Se la tua squadra ha un locale di Maven repository questa guida potrebbe essere utile per caricare il JAR lì.
Altri suggerimenti
Per una qualche ragione, non ho potuto ottenere una qualsiasi delle soluzioni di cui sopra a lavorare. (Ancora non può.)
Quello che ho fatto, invece è stato quello di includere il vaso nel mio progetto (bleah) e quindi creare una dipendenza "sistema" per esso che indica il percorso per il vaso. Probabilmente non è il modo giusto per farlo, ma funziona. E si elimina la necessità per gli altri sviluppatori del team (o la configurazione del server di build ragazzo) per mettere il vaso in loro repository locali.
Aggiorna : questa soluzione funziona per me quando ho eseguito Tools di Hibernate. Non sembra di lavorare per costruire il file WAR, però. Non include il file ojdbc6.jar nel file di destinazione WAR.
1) Creare una directory denominata "lib" nella root del vostro progetto.
2) Copiare il file ojdbc6.jar lì (qualunque sia il vaso si chiama.)
3) Creazione di una dipendenza che sembra qualcosa di simile:
<dependency>
<groupId>com.oracle</groupId>
<artifactId>ojdbc</artifactId>
<version>14</version>
<scope>system</scope>
<systemPath>${basedir}/lib/ojdbc6.jar</systemPath> <!-- must match file name -->
</dependency>
Brutto, ma funziona per me.
Per includere i file nel file di guerra aggiungere il seguente al vostro pom
<build>
<finalName>MyAppName</finalName>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<webResources>
<resource>
<directory>${basedir}/src/main/java</directory>
<targetPath>WEB-INF/classes</targetPath>
<includes>
<include>**/*.properties</include>
<include>**/*.xml</include>
<include>**/*.css</include>
<include>**/*.html</include>
</includes>
</resource>
<resource>
<directory>${basedir}/lib</directory>
<targetPath>WEB-INF/lib</targetPath>
<includes>
<include>**/*.jar</include>
</includes>
</resource>
</webResources>
</configuration>
</plugin>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.6</source>
<target>1.6</target>
</configuration>
</plugin>
</plugins>
</build>
Scarica il vaso e metterlo nel progetto src/lib. Ora è possibile utilizzare il plugin di installazione di Maven.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-install-plugin</artifactId>
<version>2.3.1</version>
<executions>
<execution>
<id>install-oracle-jdbc</id>
<goals>
<goal>install-file</goal>
</goals>
<phase>clean</phase>
<configuration>
<groupId>com.oracle</groupId>
<artifactId>ojdbc6</artifactId>
<version>11.2.0</version>
<packaging>jar</packaging>
<generatePom>true</generatePom>
<createChecksum>true</createChecksum>
<file>${project.basedir}/src/lib/ojdbc6.jar</file>
</configuration>
</execution>
</executions>
</plugin>
Ora devi solo eseguire mvn clean una volta e il lib Oracle è installato nel vostro repository Maven locale.
Oracle è ora esponendo un repository Maven a maven.oracle.com Tuttavia è necessario essere utenti registrati.
https://blogs.oracle.com/WebLogicServer/entry/weblogic_server_and_the_oracle
Secondo i commenti nel blog inserire il driver ojdbc dovrebbe essere disponibile presso le seguenti coordinate:
<groupId>com.oracle.weblogic</groupId>
<artifactId>ojdbc7</artifactId>
<version>12.1.3-0-0</version>
<packaging>jar</packaging>
Prova con:
<repositories>
<!-- Repository for ORACLE ojdbc6. -->
<repository>
<id>codelds</id>
<url>https://code.lds.org/nexus/content/groups/main-repo</url>
</repository>
</repositories>
<dependencies>
<dependency>
<groupId>com.oracle</groupId>
<artifactId>ojdbc6</artifactId>
<version>11.2.0.3</version>
</dependency>
</dependencies>
Il driver JDBC Oracle è ora disponibile in Oracle Maven Repository (non in centrale).
<dependency>
<groupId>com.oracle.jdbc</groupId>
<artifactId>ojdbc7</artifactId>
<version>12.1.0.2</version>
</dependency>
L'oracolo Maven repository richiede una registrazione utente. Le istruzioni sono disponibili in:
1. How do I find a repository (if any) that contains this artifact?
As DavidS has commented the line I quoted at the time I answered is no longer present in the current (at the time I'm writing now) OTN License Agreement agreement I linked. Consider this answer only for older version of the artifact, as the 10.2.0.3.0 and the like.
All Oracle Database JDBC Drivers are distribuited under the OTN License Agreement.
If you read the OTN License Agreement you find this license term:
You may not:
...
- distribute the programs unless accompanied with your applications;
...
so that's why you can't find the driver's jar in any public Maven Repository, because it would be distributed alone, and if it happened it would be a license violation.
Adding the dependency:
<dependency>
<groupId>com.oracle</groupId>
<artifactId>ojdbc14</artifactId>
<version>10.2.0.3.0</version>
</dependency>
(or any later version) make Maven downloads the ojdbc14-10.2.0.3.0.pom only, and in that pom you can read:
...
<licenses>
<license>
<name>Oracle Technology Network Development and Distribution License Terms</name>
<url>http://www.oracle.com/technology/software/htdocs/distlic.html</url>
</license>
</licenses>
...
which informs you about the OTN License.
2. How do I add it so that Maven will use it?
In order to make the above dependency works I agree with victor hugo who were suggesting you here to manually install the jar into your local Maven repository (the .m2 directory) by running:
mvn install:install-file -Dfile={Path_to_your_ojdbc.jar} -DgroupId=com.oracle
-DartifactId=ojdbc -Dversion=10.2.0.3.0 -Dpackaging=jar
but I want to add that the license term above doesn't limit only where you can't find the JDBC jar, but it limits where you install it too!
In fact your local Maven repository must be private and not shared because if it was shared it would be a kind of distribution in which the jar is distributed alone, even if to a little group of people into your local area network, and this represent a OTN License Agreement violation.
Moreover I think you should avoid installing the JDBC jar in your corporation repository manager (such as Artifactory or Nexus) as a single artifact because if it was installed it would be still distributed alone, even if to people in your organization only, and this represents a OTN License Agreement violation.
You can use Nexus to manage 3rd party dependencies as well as dependencies in standard maven repositories.
Up to now, its not possible to use maven repositories. I'm using ivy as dependency management tool, but also use maven2' s ibiblio repositories. And this is working for ivy:
<dependency org="oracle" name="ojdbc14" rev="10.2.0.2" conf="*->default"/>
Maven2' s dependency could be something like that:
<dependency>
<groupId>oracle</groupId>
<artifactId>ojdbc14</artifactId>
<version>10.2.0.2</version>
</dependency>
Notice that i define http://download.java.net/maven/2/ and http://mirrors.ibiblio.org/pub/mirrors/maven/mule/dependencies/maven2/[organisation]/[module]/[revision]/[artifact]-[revision].[ext] as external maven2 repos on my ivy settings.
Good news everyone! Finally we can use Oracle's official repo: https://blogs.oracle.com/dev2dev/get-oracle-jdbc-drivers-and-ucp-from-oracle-maven-repository-without-ides
Some Oracle Products support publishing maven artifacts to a local repository. The products have a plugin/maven directory which contains descriptions where to find those artifacts and where to store them. There is a Plugin from Oracle which will actually do the upload.
See: http://docs.oracle.com/middleware/1212/core/MAVEN/config_maven.htm
One of the products which may ship OJDBC in this way is the WLS, it uses however quite strange coordinates:
<groupId>com.oracle.weblogic</groupId>
<artifactId>ojdbc6</artifactId>
<version>12.1.2-0-0</version>
I ship opensource under LGPLv2 and even after several email conversations with Oracle they were unclear whether I was allowed to ship their binary JDBC driver with my distribution. The issue related to whether my license was compatible with their OTN terms so they suggested I was not permitted to ship the driver. Presumably related to this part
(b) to distribute the programs with applications you have developed to your customers provided that each such licensee agrees to license terms consistent with the terms of this Agreement
So even if you manage to publish the driver legally in your exclusive/local maven repository there is still the restriction on what you are permitted to do with that artifact. Seems absurd that even if I ship their driver in binary form along with the full OTN license file I still can't use it and must force my users to manually download the Oracle driver and drop into my library path before they can use my software.
There is one repo that provides the jar. In SBT add a resolver similar to this: "oracle driver repo" at "http://dist.codehaus.org/mule/dependencies/maven2"
and a dependency: "oracle" % "ojdbc14" % "10.2.0.2"
You can do the same with maven. pom.xml and jar are available (http://dist.codehaus.org/mule/dependencies/maven2/oracle/ojdbc14/10.2.0.2/).
If you are using Netbeans, goto Dependencies and manually install artifact. Locate your downloaded .jar file and its done. clean build will solve any issues.
For dependency
<dependency>
<groupId>com.oracle</groupId>
<artifactId>ojdbc7</artifactId>
<version>12.1.0.2</version>
</dependency>
Try
<repository>
<id>mvnrepository</id>
<url>http://nexus.saas.hand-china.com/content/repositories/rdc</url>
</repository>
SOLVED
- Please do following settings to resolve the error
This repository needs to be enable for finding Oracle 10.0.3.0 dependecies (this setting needs to be done in Buildconfig.groovy grails.project.dependency.resolver = "ivy" // or ivy
Also use following setting for compile time Oracle driver download
runtime "com.oracle:ojdbc:10.2.0.3.0"
This should solve your issue for not finding the Oracle driver for grails application
