Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You can use "system"-scope in your pom.xml for local library dependencies:</p> <blockquote> <p>system <br /> This scope is similar to provided except that you have to provide the JAR which contains it explicitly. The artifact is always available and is not looked up in a repository.</p> <p>systemPath <br/> is used only if the the dependency scope is system. Otherwise, the build will fail if this element is set. The path must be absolute, so it is recommended to use a property to specify the machine-specific path (more on properties below), such as ${java.home}/lib. Since it is assumed that system scope dependencies are installed a priori, Maven will not check the repositories for the project, but instead checks to ensure that the file exists. If not, Maven will fail the build and suggest that you download and install it manually.</p> </blockquote> <pre><code>&lt;dependency&gt; &lt;groupId&gt;some.id&lt;/groupId&gt; &lt;artifactId&gt;artifact&lt;/artifactId&gt; &lt;version&gt;1.2.3&lt;/version&gt; &lt;scope&gt;system&lt;/scope&gt; &lt;systemPath&gt;${basedir}/path/to/jarFile.jar&lt;/systemPath&gt; &lt;/dependency&gt; </code></pre> <p>AFAIK, you can use pretty much what you want for groupId, artifactId and version. See <a href="http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#System_Dependencies" rel="nofollow noreferrer">Maven System Depencies</a> and <a href="https://stackoverflow.com/questions/364114/can-i-add-jars-to-maven-2-build-classpath-without-installing-them">this</a> question.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload