Re: How to add a Jar to classpath? The jar is installed locally somewhere on the system.

[Eric Bowman]

Hi Alexander,

So you probably saw this: https://github.com/harrah/xsbt/wiki/Library-Management

If you have a build.sbt file, it's usually just a one-liner.

Suppose your project has a directory "libs", and you've put the jar or jars that are "unmanaged" in that directory.

Then just this line, separated by a blank line above & below, should do it:

unmanagedBase <<= baseDirectory { base => base / "libs" }

This will add all the jars in the "libs" directory to the compiler classpath.

Good luck,

Eric

[Alexander Obuschenko]

Eric, thanks for the reply, but unfortunately this line of code in build.sbt did change nothing:

unmanagedBase <<= baseDirectory { base => base / "libs" }

Also i found that inspect unmanaged-base returns path set to "lib" (relative to project root, i.e. project folder contains README lib project src target). And this lib folder works! All jars placed in the "lib" folder are added to the classpath and the project is compiled. But the mentioned code is not working properly :-/

[nafg]

It says there:

Manually managing dependencies involves copying any jars that you want to use to the libdirectory. sbt will put these jars on the classpath during compilation, testing, running, and when using the interpreter. You are responsible for adding, removing, updating, and otherwise managing the jars in this directory. No modifications to your project definition are required to use this method unless you would like to change the location of the directory you store the jars in.

[nafg]

Also, there's this, which may work with a file: url (haven't tried):

Explicit URL

If your project requires a dependency that is not present in a repository, a direct URL to its jar can be specified as follows:

libraryDependencies += "slinky" % "slinky" % "2.1" from "http://slinky2.googlecode.com/svn/artifacts/2.1/slinky.jar"

The URL is only used as a fallback if the dependency cannot be found through the configured repositories. Also, the explicit URL is not included in published metadata (that is, the pom or ivy.xml).