Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Gradle buildscript dependencies

People also ask

What is Buildscript in build Gradle?

buildscript: This block is used to configure the repositories and dependencies for Gradle. dependencies: This block in buildscript is used to configure dependencies that the Gradle needs to build during the project.

Where are Gradle dependencies?

Gradle declares dependencies on JAR files inside your project's module_name /libs/ directory (because Gradle reads paths relative to the build.gradle file). This declares a dependency on version 12.3 of the "app-magic" library, inside the "com.example.android" namespace group.

What is testImplementation in Gradle?

For example the testImplementation configuration extends the implementation configuration. The configuration hierarchy has a practical purpose: compiling tests requires the dependencies of the source code under test on top of the dependencies needed write the test class.


The repositories in the buildScript block are used to fetch the dependencies of your buildScript dependencies. These are the dependencies that are put on the classpath of your build and that you can refer to from your build file. For instance extra plugins that exist on the internet.

The repositories on the root level are used to fetch the dependencies that your project depends on. So all the dependencies you need to compile your project.


I want to give you clear conception. For this reason, I am attaching build.grade snapshot code for better understanding.

buildscript dependencies:

buildscript {
    repositories {
        maven { url("https://plugins.gradle.org/m2/") }
    }

    dependencies {
        classpath 'net.saliman:gradle-cobertura-plugin:2.3.2'
        classpath 'com.netflix.nebula:gradle-lint-plugin:latest.release'
    }
}

root level/core dependencies:

repositories{
    mavenLocal()
    maven { url("https://plugins.gradle.org/m2/") }
    maven { url "https://repo.spring.io/snapshot" }
}

dependencies {
        //Groovy
        compile group: 'org.codehaus.groovy', name: 'groovy-all', version: '2.3.10'

        //Spock Test
        compile group: 'org.spockframework', name: 'spock-core', version: '1.0-groovy-2.3'

        //Test
        testCompile group: 'junit', name: 'junit', version: '4.10'
        testCompile group: 'org.testng', name: 'testng', version: '6.8.5'
}

So, First I want to clarify in single word that

i) buildscript dependencies jar file will be downloaded from buildscript repositories.[Project external dependency]

ii) root level dependencies jar file will be downloaded from root level repositories.[For project dependency]

Here,

The “buildscript” block only controls dependencies for the buildscript process itself, not for the application code. As various gradle plugin like gradle-cobertura-plugin, gradle-lint-plugin are found from buildscript repos. Those plugins would not be referenced as dependencies for the application code.

But for project compilation and test running jar files like groovy all jar, junit and testng jar will be found from root level repositories.

And another thing, maven { url("https://plugins.gradle.org/m2/") } portion can be used in both blocks. Because they are used for different dependencies.

Resource Link: Difference between dependencies within buildscript closure and core