Still getting warning : Configuration 'compile' is obsolete and has been replaced with 'implementation'

configuration 'testcompile' is obsolete and has been replaced with 'testimplementation'.
the following project options are deprecated and have been removed:
dsl element dexoptions incremental is obsolete and will be removed at the end of 2018
the specified android sdk build tools version is ignored
compilesdkversion deprecated
androidtestimplementation error
compile replaced with implementation
android gradle plugin warning

I have replaced every occurrence of compile by implementation in my project's build.gradle, but I'm still getting this warning :

I tried to look for "compile " in the whole project but no match was found. So what could be the cause?

I've updated com.google.gms:google-services from 3.1.1 to 3.2.0 and the warning stopped appearing.

buildscript {

    repositories {
        google()
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.1.0'

    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files

    classpath 'com.google.gms:google-services:3.2.0'
    }
}

Warning, Configuration 'compile' is obsolete and has been replaced with 'implementation' If the warning still persists, try to rebuilt the solution after deleting the build folder. Run with --info or --debug option to get more log output. Still getting warning : Configuration 'compile' is obsolete and has been replaced with 'implementation'

I have one same Warning caused to com.google.gms:google-services.

The solution is to upgrade classpath com.google.gms:google-services to classpath 'com.google.gms:google-services:3.2.0' in file in build.gradle Project:

buildscript {
    repositories {
        jcenter()
        google()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.1.0'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
        classpath 'com.google.gms:google-services:3.2.0'
    }
}

allprojects {
    repositories {
        jcenter()
        google()
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

In Android Studio verion 3.1 dependencies complie word is replaced to implementation

dependencies with Warning in android studio 3.1

dependencies {
            compile fileTree(dir: 'libs', include: ['*.jar'])
            compile 'com.android.support:appcompat-v7:27.1.0'
            compile 'com.android.support.constraint:constraint-layout:1.0.2'
            testImplementation 'junit:junit:4.12'
            androidTestImplementation 'com.android.support.test:runner:1.0.1'
            androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.1'
    }

dependencies OK in android studio 3.1

    dependencies {
            implementation fileTree(dir: 'libs', include: ['*.jar'])
            implementation 'com.android.support:appcompat-v7:27.1.0'
            implementation 'com.android.support.constraint:constraint-layout:1.0.2'
            testImplementation 'junit:junit:4.12'
            androidTestImplementation 'com.android.support.test:runner:1.0.1'
            androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.1'

    }

Gradel generate by Android Studio 3.1 for new project.

Visit https://docs.gradle.org/current/userguide/dependency_management_for_java_projects.html

For details https://docs.gradle.org/current/userguide/declaring_dependencies.html

Error Configuration 'compile' is obsolete and has been replaced with , It will be removed at the end of 2018 Configuration 'testCompile' is obsolete and has been replaced with Also if the gradle sync is still failing:. WARNING: Configuration 'compile' is obsolete and has been replaced with 'implementation' and 'api'. Hi, I have the same problem , plz help me have android 3.1.4 'gradle version 4.4' 'build.grandle'

I've updated com.google.gms:google-services from 3.2.0 to 3.2.1 and the warning stopped appearing.

 buildscript {

    repositories {
        google()
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.1.1'
        classpath 'com.google.gms:google-services:3.2.1'

    }
}

Still getting warning : Configuration 'compile' is obsolete and has , Still getting warning : Configuration 'compile' is obsolete and has been replaced with 'implementation'. the following project options are deprecated and have  Solution: IE's Enhanced Security Configuration can be turned on by each user, even if the overall setting is "off". For the user who has it on, check the Hi, I have this funny problem, where IE ESC is turned off on a Windows 2012 R2 server, but IE says it is turned on.I have 2 users, which needs access to a BI server, to be able

Using the currently latest version of the google gms services resolved it for me.

In the project level build.gradle:

buildscript {
    ...
    dependencies {
        classpath 'com.google.gms:google-services:3.2.1'
        ...  
    }
}

Android Studio 3.1.0, Hello Everyone, I am doing my Final Year Project (FYP) and today I updated my Gradle version on Android Studio to 3.1.0 and I am not sure  In the Configuration Manager console navigate to Administration > Site Configuration > Sites, and then select the site where you want to configure the status system. On the Home tab, in the Settings group, click Configure Site Components , and select Status Reporting .

Open up your build.gradle file located here:

This is the old way of writing the dependency libraries (for gradle version 2 and below):

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    testCompile 'junit:junit:4.12'
    compile files('libs/volley.jar')
    compile 'com.android.support:support-v4:21.+'
}

This is the new (right) way of importing the dependencies for gradle version 3:

dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    testImplementation 'junit:junit:4.12'
    implementation files('libs/volley.jar')
    implementation 'com.android.support:support-v4:21.+'
}

Add build dependencies, WARNING: Configuration 'androidTestApi' is obsolete and has been on the compile classpath to Library A version 1.0, and you still get an error similar to the​  I'm aware of the point and print section, I'm not concerned with shared printers, but local installs. When I add the users to the Network Configuration Operators group I still get a UAC prompt, but you can enter the user's credentials and they're accepted. I'm trying to find out whether this is expected. – BlueCompute Nov 4 '14 at 22:21

How to fix this error 'Configuration 'compile' is obsolete and has , If you already have made changes mentioned as above and still getting same error, you can try below mentioned troubleshooting steps : Add jcenter() repository  So the reason that I was still getting the task waiting indication was because the components were still there, and it thought it still needed to do the initial promotion. On a whim after reading Daniel's post, I checked the remove role wizard, and AD was in fact still listed.

React-native-auth0: WARNING: Configuration 'compile' is obsolete , I'm running version 1.4.2 and getting the following warning when with implementation but I still get this message for react-native-auth0 . The Configuration Manager console is always installed on every site server. You can also install it on other computers. For more information, see Install the Configuration Manager console. The simplest method to open the console on a Windows 10 computer, press Start and start typing Configuration Manager console.

Upgrading your build from Gradle 5.x to 6.0, This is so that you can see any deprecation warnings that apply to your build. The usage of the compile and runtime configurations in the Java ecosystem The legacy behaviour of Gradle, prior to 5.0, was still in place instead of being Status Page. Products. Build Scans · Build Cache · Enterprise Docs. Get Help. We created the alias manually first using SQL Server Configuration Manager. Under SQL Native Client 11.0 (32bit) --> Alias and SQL Native Client 11.0 Con --> Alias (you need to do both sections), right click, new alias type your alias name "SharePointDB" and fill out the parameters.

Comments
  • Are you using a local library that is using 'compile' still?
  • @Devsil possibly... but how can I find out which one? I tried a Find in Path in the whole project but couldn't find any occurrence of compile..
  • If you are using a local library you will see its gradle.build file located in the project viewer on the right side of your Android Studio window. In that build.gradle file it may contain a "compile" as opposed to implementation. If any build.gradle file you see there doesn't contain that. It may be a library you are using that isn't local thus not giving you access to change that. So this warning can just be ignore for now.
  • Gradle should give the line number where the problem is occuring
  • try it : stackoverflow.com/questions/48623244/… and for Failed to resolve: android.arch.persistence.room:runtime:1.1.1 Open File Show in Project Structure dialog try to change version to 1.0.0
  • Configuration 'compile' is obsolete and has been replaced with 'implementation'. It will be removed at the end of 2018 To be clear am not using any google service dependencies { classpath 'com.android.tools.build:gradle:3.1.0' }
  • I get "Could not find com.google.gms:google-services:3.2.0." when I try this. Update: changing it manually triggered lint warning when I changed it back to 3.1.1, then Alt+Enter to apply fix automagically changed it to com.google.gms:google-services:3.2.0 with no errors on sync. I'm not sure what the difference was but it's frustrating.
  • Alright, I believe I understand the difference. I had changed the Project and Module build.gradle gms classpath to version 3.2.0. It's the Module change that caused the problem. Change only the Project build.gradle gms classpath version.
  • I was also missing jcenter() repo! The project was very old and did not have that repo included!
  • Do you mean that I should just add that line manually to the file?
  • Note that "testCompile" changes to "testImplementation".
  • most of the answers , and the most popular one as well , are all focusing on com.google.gms:google-services but it's all about updating the old naming style in both gradle files
  • you just need to change the version like I have this 'com.google.gms:google-services:3.2.0' you need to do just replace 3.2.0 with 3.2.1.
  • Thanks, I had updated the wrong class, that's why I got the error.