Use conventions instead of cross-project configuration

gradle userguide suggests to avoid allprojects/subprojects and use conventions instead

https://docs.gradle.org/current/userguide/sharing_build_logic_between_subprojects.html#sec:convention_plugins_vs_cross_configuration
This commit is contained in:
Manuel Fuhr 2024-04-05 23:11:58 +02:00
parent b8929ab414
commit 5d4065d141
15 changed files with 80 additions and 70 deletions

View file

@ -1,7 +1,6 @@
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
mavenCentral()
google()
@ -9,57 +8,11 @@ buildscript {
dependencies {
classpath 'com.android.tools.build:gradle:8.3.1'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
// NOTE:
// there are four places to change the version number
// this file
// app: build.gradle (versionCode only)
// OsmTrack (version and versionDate)
// docs revisions.md (version and versionDate)
project.version "1.7.3"
group 'org.btools'
repositories {
mavenCentral()
google()
}
apply plugin: "maven-publish"
publishing {
repositories {
maven {
name = "GitHubPackages"
url = uri("https://maven.pkg.github.com/$System.env.REPO")
credentials {
username = project.findProperty("gpr.user") ?: System.getenv("USERNAME")
password = project.findProperty("gpr.key") ?: System.getenv("TOKEN")
}
}
}
publications {
gpr(MavenPublication)
}
}
apply plugin: "checkstyle"
apply plugin: "pmd"
pmd {
consoleOutput = true
toolVersion = "7.0.0"
rulesMinimumPriority = 5
ruleSetFiles = files("${rootProject.rootDir}/config/pmd/pmd-ruleset.xml")
ruleSets = []
// ignoreFailures = true
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}