The MAVEN project introduced SQLJDBC4 the perfect solution for not finding a package.

Today I met this problem, solved it, and by the way make a record. First of all to reproduce this problem, maven install error, said that can't find this package, but in fact I have installed.

Let's take a look at what's in Maven's local repository, which means that our package is not downloaded at all, and that we can download the jar package first and then install the jar packages with MVN installs, but it's too cumbersome and the problem isn't fundamentally solved.

Let's look at the introduction in Maven, so what is Clojars? It turned out to be another separate warehouse.

The following is the perfect solution, online said the more chaotic. In fact, just add a repository on the line, and then re-clean install the perfect solution.

    <repositories>        <repository>            <id>clojars</id>            <url>http://clojars.org /repo/</url>        </repository>    </repositories>

　　

This approach also applies to some artifacts solutions for other non-MAVEN official warehouses. In fact, we can infer that even if you are downloading from the MAVEN official website jar package, also point to the third-party website, understand this, you can extrapolate.

The MAVEN project introduced SQLJDBC4 the perfect solution for not finding a package.