CODEWITHSUNDEEP
gradle
Christian Goetze
Christian Goetze

Reputation: 2414

Do gradle configurations merge or override?

Say I define a plugin, like so:

import org.gradle.api.artifacts.dsl.RepositoryHandler
import org.gradle.api.artifacts.repositories.MavenArtifactRepository
import org.gradle.api.Project
import org.gradle.api.Plugin

class MyRepos implements Plugin<Project> {
    static final String NEXUS_URL = 'http://nexus.mine.com/nexus/content/repositories/'
    static final List<String> NEXUS_REPOS = [
        'central',
        'build',
        'snapshots',
        'release-candidates',
        'releases',
    ]

    void apply(Project project) {
        project.repositories {
            NEXUS_REPOS.each {
                maven {
                    url (NEXUS_URL + it)
                }
            }
            mavenLocal()
        }
        project.buildscript {
            repositories {
                maven {
                    url (NEXUS_URL + 'central')
                }
                mavenLocal()
            }
        }
    }
}

and in a local build.gradle, I write

apply plugin: MyRepos

buildscript {
    dependencies {
       ...
    }
}

My desire is for the two buildscript sections to be merged such that the repositories are defined in the plugin and the dependencies in build.gradle, but it appears that the local declaration overrides the plugin and I end up with an error indicating "no repositories defined".

If I do this via configuration injection from the top level build.gradle, is the result the same?

Maybe the right solution is for the plugin to provide an ext closure to define useMyRepos() similar to the way mavenCentral() is used...

Upvotes: 1

Views: 2902

Answers (1)

Amnon Shochot
Amnon Shochot

Reputation: 9386

Generally configuration items in gradle are merged so you can apply configurations in different locations. You can, for example, configure some of the dependencies in one build script that will be applied to another build script that will add additional dependencies.

However, your case is a bit different since you're using buildScript configuration which is can be used to define the dependencies for the build script itself rather than the root repositories node which is intended for defining the dependencies of the project you build.

In this case, according to Purpose of buildScript in Gradle as these are different configurations you'll have to define your dependency twice.

Upvotes: 1

Related Questions