Find Oracle JDBC driver in Maven repository

前端 未结 22 1804
你的背包
你的背包 2020-11-22 09:28

I want to add the oracle jdbc driver to my project as dependency (runtime scope) - ojdbc14. In MVNrepository site the dependency to put in the POM is:



        
22条回答
  •  南方客
    南方客 (楼主)
    2020-11-22 10:11

    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:

    
        com.oracle
        ojdbc14
        10.2.0.3.0
    
    

    (or any later version) make Maven downloads the ojdbc14-10.2.0.3.0.pom only, and in that pom you can read:

    ...
    
        
            Oracle Technology Network Development and Distribution License Terms
            http://www.oracle.com/technology/software/htdocs/distlic.html
        
    
    ...
    

    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.

提交回复
热议问题