We Keep Coding

Building a jar file from a gradle dependency

I need to make dex file from my android project. First, i need to compile my classes to jar. But i need dependencies in jar. otherwise, i'll get about 300 errors because of unknown methods. I need Timber in jar. but i can't find it in the internet. I searched a lot, but no luck. This is the link to the source code in github.
https://github.com/JakeWharton/timber
How do i build a jar from this gradle project?

To add gradle library to your project, you need to add implementation "package-group:package-name:package-version" to your build.gradle.
For Timber, you would do implementation "com.jakewharton.timber:timber:4.7.1".
If you want to compile your project, with its dependencies into a jar, then you want to look up "fat jars". Gradle Shadowjar is a plugin that does this.

Include sources from Java library submodule in Android library project aar artifact

I have a java library submodule holding interfaces which are used in another android library submodule. The problem is that the sources of the java library module are compiled but not included in the aar artifact of the android library project.
How can I include the sources of the java library in the android library aar file?

I ended up including the source files of the java library directly into the android library project using:
sourceSets {
main{
java {
srcDir("../java_library/src")
}
}
}
Only this way the sources are included in the aar file. Still will be great to know if it is possible using simple gradle dependency management.

is it possible to generate an Android library AAR archive with Gradle, automatically fulfilled with maven JARs dependecies?

I would like to find out the best way in order to generate with Gradle an Android Library AAR archive containing all the dependencies resolved by maven, thus the application doesn't have to include those dependencies, just import the AAR and everything is configured by the android library.
The jars should be placed by the Gradle task in the AAR libs/ dir.
I was doing this, before the new AAR system, with a JAR containing multiple source sets, just because it was not possible to assemble a binary android library.

Why does Gradle only include classes from my library with project dependency

I'm building an Android app that has a dependency on a custom library, and Gradle is only willing to include my custom library when I use a project dependency, not when I use a files dependency to include the library's jar file. I'm building both my app and the library with the API levee 19 SDK.
failing dependencies section from build.gradle:
dependencies {
compile 'com.android.support:appcompat-v7:+'
compile files('libs/MyLibrary.jar')
}
If I use the above dependencies section, none of the class in MyLibrary.jar are included in the build apk file, as verified by extracting its classes.dex and running dexdump. I have also verified that all of the classes are present in the jar file I'm using.
If I use the following dependencies section, then all of the classes in MyLibrary are included in the apk file:
dependencies {
compile 'com.android.support:appcompat-v7:+'
compile project(':MyLibrary')
}
I'm using Android Studio 0.4.0, Gradle 1.9, and I think the Gradle plugin 0.7.1.
What is going on here? I'd really like to build my app with the API level 18 sdk to test compatibility, but I can't get that working unless I'm able to just use the jar file for my library.

Okay, this was my fault. My library's build.gradle was configured to only include the source files in the jar output file. The following is incorrect Gradle code and will give you the same problems as I've had.
task jar(type: Jar) {
from android.sourceSets.main.java
}
This answer shows how to fix the jar file creation. It's ugly, but it seems to work.

Jar task does not include dependencies in the final jar artifact.
From Gradle documentation on jar task:
The jar task creates a JAR file containing the class files and
resources of the project.
It assumes that since you are building jar for your project, all dependencies will be provided during runtime. As opposed to war, where all dependencies are usually included in the final artifact.
If you need to create "fat jar", which will include the dependencies, then look into specific plugins, for example gradle-fatjar-plugin.

It's a little bit of a longshot, but if you're not using Android Studio 0.4.0 and you've just added the jar file, try cleaning your project and rebuilding from scratch. We've seen this bug: https://code.google.com/p/android/issues/detail?id=63366 where libraries don't get included without cleaning the project, though this bug refers to a dependency downloaded from Maven and not a local jar file (which may or may not be an important difference). This was fixed in Android Studio 0.4.0 (more specifically, in the Gradle plugin 0.7.0).

Gradle 2 android projects using same library

I have the following structure
MainProjectRoot
Android Project 1:
...
Android Project 2:
...
Shared Library:
...
The library project is shared between both of the Android projects. I am trying to convert things to work with the new build system.
This is what export from eclipse generated for the build.gradle for Project1.
compile project(':D::workspace:MainProjectRoot:shared-library')
How do i fix this reference?
i tried this but it expects the library to be inside the Project1 Folder if i leave it out as
compile project(':shared-library')

The export from Eclipse is broken on Windows when dealing with multi-module projects. We are fixing this.
In the meantime ensure you have the settings.gradle file under MainProjectRoot/
It should contain:
include 'project1'
include 'project2'
include 'shared-library'
(or whatever those folder names are).
Then you change the dependency line to be
compile project(':shared-library')