# Jar \(via HTTP or S3\)

If you have external jars that need to be downloaded into your project, you can use the `jar:` endpoint with an HTTP or S3 URL to download them. When a S3 path is specified, authentication is handled in the same fashion as with the S3 endpoint.

The jar endpoint does not expect the jars to be contained in a zip file or to have a box.json. As such, there is no real package slug or name, so CommandBox will "guess" the name based on the name of the jar \(if a jar name appears in the path or query string\).

```text
install jar:http://site.com/path/to/file.jar
install "jar:https://github.com/coldbox-modules/cbox-bcrypt/blob/master/modules/bcrypt/models/lib/jbcrypt.jar?raw=true"
install "jar:https://search.maven.org/remotecontent?filepath=jline/jline/3.0.0.M1/jline-3.0.0.M1.jar"
install jar:s3://my-private-bucket/path/to/file.jar
```

## Installation path

Files from the `jar:` endpoint will be placed in a `lib/` folder by default unless you provide another folder for installation.

## In box.json

You can specify jars as dependencies in your `box.json` in this format.

```javascript
{
    "dependencies":{
        "jline-3.0.0.M1":"jar:https://search.maven.org/remotecontent?filepath=jline/jline/3.0.0.M1/jline-3.0.0.M1.jar",
        "jbcrypt":"jar:s3://my-private-bucket/path/to/jbcrypt.jar"
    }
}
```

Note this installation method does not include any dependencies of the jar like a Maven installation would. That will be a future endpoint.