Jean-Luc Makiola
e4c8dbf2c1
All checks were successful
CI / ci (push) Successful in 8m7s
The Gradle Java-toolchain auto-download resolver can fetch a JDK at build time, which an offline / reproducible F-Droid build scanner rejects. It was unused — modules set jvmTarget directly with no toolchain block — so removing it is a no-op for the build and brings Agendula in line with floret-kit's no-resolver rule. Clean assembleDebug verified. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
30 lines
791 B
Kotlin
30 lines
791 B
Kotlin
pluginManagement {
|
|
repositories {
|
|
google {
|
|
content {
|
|
includeGroupByRegex("com\\.android.*")
|
|
includeGroupByRegex("com\\.google.*")
|
|
includeGroupByRegex("androidx.*")
|
|
}
|
|
}
|
|
mavenCentral()
|
|
gradlePluginPortal()
|
|
}
|
|
}
|
|
|
|
// No Gradle Java-toolchain auto-download resolver plugin: it can fetch a JDK at
|
|
// build time, which an offline / reproducible F-Droid build scanner rejects.
|
|
// Modules set jvmTarget directly, so no toolchain resolver is needed.
|
|
|
|
dependencyResolutionManagement {
|
|
repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
|
|
repositories {
|
|
google()
|
|
mavenCentral()
|
|
}
|
|
}
|
|
|
|
rootProject.name = "Agendula"
|
|
include(":app")
|
|
includeBuild("floret-kit")
|