title: CommandError: You appear to have guava-jdk5 on your project buildScript or buildSrc classpath
body: <p>Hi i had updated my IDE "Android Studio 3.0" and Build.gradle too but i encountered a problem in <strong>Build Build.gradle (Module APP)</strong> </p>
  
  <p><strong>Build.gradle (Module APP) after Update it became like this</strong> </p>
  
  <pre><code>    apply plugin: 'com.android.application'
  
  android {
      compileSdkVersion 26
      buildToolsVersion '25.0.0'
      defaultConfig {
          applicationId "com.abdeljalilkchih.learnarabicforkids"
          minSdkVersion 12
          versionName "\n" +
                  "        targetSdkVersion 26\n" +
                  "        versionCode 1515.0"
          testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
      }
      buildTypes {
          release {
              minifyEnabled false
              proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
          }
      }
  }
  
  dependencies {
      compile fileTree(dir: 'libs', include: ['*.jar'])
      androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2', {
          exclude group: 'com.android.support', module: 'support-annotations'
      })
      compile 'com.android.support:appcompat-v7:26.1.0'
      compile 'com.android.support.constraint:constraint-layout:1.0.0-beta1'
      compile 'com.google.firebase:firebase-core:10.0.1'
      compile 'com.google.firebase:firebase-auth:10.0.1'
      compile 'com.google.firebase:firebase-ads:10.0.1'
      compile 'com.akexorcist:RoundCornerProgressBar:2.0.3'
      testCompile 'junit:junit:4.12'
  }
  apply plugin: 'com.google.gms.google-services'
  </code></pre>
  
  <p><strong>Message Gradle sync</strong></p>
  
  <pre><code>    Error:(1, 0) You appear to have guava-jdk5 on your project buildScript or buildSrc classpath.
  This is likely a transitive dependency of another gradle plugin.Run the buildEnvironment task to find out more.
  See https://issuetracker.google.com/38419426#comment8 for a workaround.
  </code></pre>