Martin Kolesar
03/15/2023, 10:02 AMxxfast
03/15/2023, 10:03 AMMartin Kolesar
03/15/2023, 10:04 AMxxfast
03/15/2023, 10:05 AMMartin Kolesar
03/15/2023, 10:06 AMxxfast
03/15/2023, 10:08 AMimplementation(project(":module-name")
Martin Kolesar
03/15/2023, 10:13 AMMaarten Bruggeman
03/15/2023, 10:15 AMMartin Kolesar
03/15/2023, 10:15 AMMaarten Bruggeman
03/15/2023, 10:19 AMxxfast
03/15/2023, 10:20 AMbuild.gradle
looks like for the project and each of the modules? Looks like it is misconfigured somewhereMartin Kolesar
03/15/2023, 10:21 AMxxfast
03/15/2023, 10:26 AMdependencyResolutionManagement
with this?
dependencyResolutionManagement {
repositories {
google()
mavenCentral()
}
}
}
Martin Kolesar
03/15/2023, 10:32 AMxxfast
03/15/2023, 10:35 AMrepositoriesMode.set(RepositoriesMode.PREFER_SETTINGS)
RepositoriesMode.PREFER_SETTINGS
actually does, but that seems to break the order of how the dependencies are looked up from each repositoryMartin Kolesar
03/15/2023, 10:38 AMxxfast
03/15/2023, 10:39 AMMartin Kolesar
03/15/2023, 10:40 AMxxfast
03/15/2023, 10:42 AMAdam S
03/15/2023, 2:21 PMdependencyResolutionManagement
yet
https://youtrack.jetbrains.com/issue/KT-51379
You can add the repositories manually though
https://github.com/Kantis/ks3/blob/7ae763fc9fac4cfab63c153261b281c6066d5c8f/build-logic/repositories.gradle.kts#L37-L65Jeff Lockhart
03/15/2023, 2:38 PMrepositoriesMode.set(RepositoriesMode.PREFER_SETTINGS)
just tells gradle to use the repositories defined in settings.gradle.kts in dependencyResolutionManagement
preferably over a repositories
block defined in a specific project's build.gradle.kts. It's a newer gradle feature.
You can use the older method to define repositories for all projects, without forcing projects to not be able to add their own repositories by removing the dependencyResolutionManagement
block in settings.gradle.kts and adding them under
allprojects {
repositories {
google()
mavenCentral()
maven { url '<https://jitpack.io|https://jitpack.io>' }
}
}
in your top-level build.gradle.kts.