I had a closer look at your build.gradle and it seems that paths are a little bit off. You specify source as src/model, yet your project structure and Java source suggest that model is your package name, which means the source declaration should be: main { java { srcDir ‘src’ } } Same for tests: … Read more
Just Change your line breaks , it will solve your problem dependencies { compile ‘com.android.support:appcompat-v7:23.4.0’ compile ‘com.parse.bolts:bolts-tasks:1.3.0’ compile ‘com.parse:parse-android:1.13.0’ compile ‘com.google.android.gms:play-services:9.2.1’ } break line after each dependencies. See answer here : https://stackoverflow.com/a/33991915/4985413
I resolve this issue by moving maven {url “https://maven.google.com”} before jcenter(), like this: repositories { maven { url “https://maven.google.com” } jcenter() maven { url ‘https://jitpack.io’ } } This is because I find jcenter() repository has deleted the directory of android.arch.core, so we have to get this file (android.arch.core:common-1.1.0.jar) from “https://maven.google.com”
In your utility (data) projects put: bootJar { enabled = false } jar { enabled = true } If kotlin dsl tasks.getByName<BootJar>(“bootJar”) { enabled = false } tasks.getByName<Jar>(“jar”) { enabled = true }
The problem was that another compile object was also dependent on the first level dependency that had the guava-jdk5 as a transitive dependency, so this other object was bringing in the unwanted module. I was able to finally see this using ./gradlew -q :app:dependencyInsight –dependency guava –configuration compile and could exclude it using configurations { … Read more
This solution may only work in Iran. If you know that’s working out of Iran, please let others know. Why would a proxy be necessary? There have been a number of technology-related sanctions against Iran. Windows go to -> File | Settings | Appearance & Behavior | System Settings | HTTP Proxy, and choose -> … Read more
Showing the resolved dependencies for the build script class path isn’t a built-in operation as for other configurations (which can be inspected with gradle dependencies). However, you can write a task to do so. For example: task showClasspath { doLast { buildscript.configurations.classpath.each { println it.name } } } A variation that just shows the Android … Read more
As the error message suggests you are not excluding the META-INF/LICENSE file which exists in more than one of your dependencies com.android.build.api.transform.TransformException: com.android.builder.packaging.DuplicateFileException: Duplicate files copied in APK META-INF/LICENSE packagingOptions { exclude ‘META-INF/NOTICE’ // will not include NOTICE file exclude ‘META-INF/LICENSE’ // will not include LICENSE file // as noted by @Vishnuvathsan you may also … Read more
gradlew is not in your global path. To execute the ‘clean’ task (or any task for that matter) using the gradle wrapper (gradlew) in your project directory in your terminal, specify the current directory with the ‘./’: ./gradlew clean
compileOnly is the replacement — the equivalent configuration that is being deprecated is provided. See the documentation.