# LaVOZs

The World’s Largest Online Community for Developers

'; java - How to add local .jar file dependency to build.gradle file? - LavOzs.Com

So I have tried to add my local .jar file dependency to my build.gradle file:

apply plugin: 'java'

sourceSets {
main {
java {
srcDir 'src/model'
}
}
}

dependencies {
runtime files('libs/mnist-tools.jar', 'libs/gson-2.2.4.jar')
runtime fileTree(dir: 'libs', include: '*.jar')
}


And you can see that I added the .jar files into the referencedLibraries folder here: https://github.com/WalnutiQ/wAlnut/tree/version-2.3.1/referencedLibraries

But the problem is that when I run the command: gradle build on the command line I get the following error:

error: package com.google.gson does not exist


Here is my entire repo: https://github.com/WalnutiQ/wAlnut/tree/version-2.3.1

If you really need to take that .jar from a local directory,

repositories {
flatDir {
dirs 'libs'
}
}

dependencies {
implementation name: 'gson-2.2.4'
}


However, being a standard .jar in an actual maven repository, why don't you try this?

repositories {
mavenCentral()
}
dependencies {
}


According to the documentation, use a relative path for a local jar dependency as follows:

dependencies {
implementation files('libs/something_local.jar')
}


You could also do this which would include all JARs in the local repository. This way you wouldn't have to specify it every time.

dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
}


The following works for me:

compile fileTree(dir: 'libs', include: '*.jar')


• Install the jar into your local Maven repository:

mvn install:install-file -Dfile=utility.jar -DgroupId=com.company -DartifactId=utility -Dversion=0.0.1 -Dpackaging=jar

• Check that you have the jar installed into your ~/.m2/ local Maven repository

• Enable your local Maven repository in your build.gradle file:

repositories {
mavenCentral()
mavenLocal()
}

dependencies {
implementation ("com.company:utility:0.0.1")
}

• Now you should have the jar enabled for implementation in your project

The accepted answer is good, however, I would have needed various library configurations within my multi-project Gradle build to use the same 3rd-party Java library.

Adding '$rootProject.projectDir' to the 'dir' path element within my 'allprojects' closure meant each sub-project referenced the same 'libs' directory, and not a version local to that sub-project: //gradle.build snippet allprojects { ... repositories { //All sub-projects will now refer to the same 'libs' directory flatDir { dirs "$rootProject.projectDir/libs"
}
mavenCentral()
}

...
}


EDIT by Quizzie: changed "${rootProject.projectDir}" to "$rootProject.projectDir" (works in the newest Gradle version).

A simple way to do this is

compile fileTree(include: ['*.jar'], dir: 'libs')


it will compile all the .jar files in your libs directory in App.

I couldn't get the suggestion above at https://stackoverflow.com/a/20956456/1019307 to work. This worked for me though. For a file secondstring-20030401.jar that I stored in a libs/ directory in the root of the project:

repositories {
mavenCentral()
// Not everything is available in a Maven/Gradle repository.  Use a local 'libs/' directory for these.
flatDir {
dirs 'libs'
}
}

...

compile name: 'secondstring-20030401'


A solution for those using Kotlin DSL

The solutions added so far are great for the OP, but can't be used with Kotlin DSL without first translating them. Here's an example of how I added a local .JAR to my build using Kotlin DSL:

dependencies {
compile(files("/path/to/file.jar"))
testCompile(files("/path/to/file.jar"))
testCompile("junit", "junit", "4.12")
}


Remember that if you're using Windows, your backslashes will have to be escaped:

...
compile(files("C:\\path\\to\\file.jar"))
...


And also remember that quotation marks have to be double quotes, not single quotes.

The Question already has been answered in detail. I still want to add something that seems very surprising for me:

The "gradle dependencies" task does not list any file dependencies. Even though you might think so, as they have been specified in the "dependencies" block after all..

So don't rely on the output of this to check whether your referenced local lib files are working correctly.

The solution which worked for me is the usage of fileTree in build.gradle file. Keep the .jar which need to add as dependency in libs folder. The give the below code in dependenices block in build.gradle:

dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
}


The best way to do it is to add this in your build.gradle file and hit the sync option

dependency{
compile files('path.jar')
}


For gradle just put following code in build.gradle:

dependencies {
...
compile fileTree(dir: 'lib', includes: ['suitetalk-*0.jar'])
...
}


and for maven just follow steps:

For Intellij: File->project structure->modules->dependency tab-> click on + sign-> jar and dependency->select jars you want to import-> ok-> apply(if visible)->ok

Remember that if you got any java.lang.NoClassDefFoundError: Could not initialize class exception at runtime this means that dependencies in jar not installed for that you have to add all dependecies in parent project.

Goto File -> Project Structure -> Modules -> app -> Dependencies Tab -> Click on +(button) -> Select File Dependency - > Select jar file in the lib folder

Very Simple

Be careful if you are using continuous integration, you must add your libraries in the same path on your build server.

For this reason, I'd rather add jar to the local repository and, of course, do the same on the build server.

An other way:

Add library in the tree view. Right click on this one. Select menu "Add As Library". A dialog appear, let you select module. OK and it's done.