Import class from 3rd Party Library. Android Studio 3.1, Gradle 3.1

Question

After updating Android Studio and gradle to 3.1, I changed all compile statements to implementation. But when I build, android studio cannot resolve imports found in 3rd party libraries.

Scenario: Main projects imports sub-module which also import a jar file.

When I try to import a class from the jar file into the main project, android studio is not able to resolve it.

How can I import the single file without having to add the jar file as a dependency in the main project?

use `api` instead it is the new `compile` or have the dependency directly in your main project — Nongthonbam Tonthoi, Apr 03 '18 at 10:49
that didn't work, plus will it be possible to do it without having to import the whole library again? — Bubunyo Nyavor, Apr 03 '18 at 10:52
@NongthonbamTonthoii figured it out, the trick is to change the `implementation` of the jar file import to the `api`. I was changing if for the module import earlier. Please add it as an answer so I can select it as the right answer. — Bubunyo Nyavor, Apr 03 '18 at 11:47

score 2 · Accepted Answer · answered Apr 03 '18 at 12:01

You should use api instead, it is the new compile or have the dependency directly in your main project. Just changing implementation to api will fix the issue but you consider using implementation wherever possible to improve build time.

You can see the difference between api and implemenation here.

score 1 · Answer 2 · answered Apr 03 '18 at 14:05

The answer by @nongthonbam-tonthoi is correct but he does not explain why.

Short version

Implementation - hide this dependency from other modules(that depend on this module). if B depends on A, it cannot use any dep declared in A using implementation.

api - Make this available to other modules that depend on this module.i.e if you add say GSON as a dep in module A using api rather than implementation, all other modules that depend A can use GSON without declaring it again.

Long version

implementation is a way of declaring dependencies for only a given module. What this means is that, the dependency can only be used in that particular module. compile on the other hand "leaks" the dependencies to other modules so you can import and use the classes that dep brings in other modules. If you want this behavior, the new way of doing it is to use api.

This change is particularly targeted at multi-module projects as it can help gradle avoid re-compiling a module during a build when it does not change.

However if you're migrating from an old project, chances are you are (ab)using compile to use dependencies declared in other modules without explicitly declaring them again.

You can keep using compile but remember that it's is deprecated and will be removed soon.

See here for a deeper explanation.

score 0 · Answer 3 · answered Apr 06 '18 at 17:51

Edit build.gradle (Module:app) and change SDK version to 27.1.1 Eg:

defaultConfig {
        applicationId "com.projectname"
        minSdkVersion 15
        targetSdkVersion 27
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }

implementation 'com.android.support:appcompat-v7:27.1.1'

and rebuild the project and restart android studio

Import class from 3rd Party Library. Android Studio 3.1, Gradle 3.1

3 Answers3