Use directory name as project name for libs (#115720)

The libs projects are configured to all begin with `elasticsearch-`.
While this is desireable for the artifacts to contain this consistent
prefix, it means the project names don't match up with their
directories. Additionally, it creates complexities for subproject naming
that must be manually adjusted.

This commit adjusts the project names for those under libs to be their
directory names. The resulting artifacts for these libs are kept the
same, all beginning with `elasticsearch-`.
This commit is contained in:
Ryan Ernst 2024-10-29 13:02:28 -07:00 committed by GitHub
parent 06eb0727c2
commit e5d5c17c99
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
66 changed files with 165 additions and 136 deletions

View file

@ -13,19 +13,19 @@ apply plugin: 'elasticsearch.mrjar'
dependencies {
// This dependency is used only by :libs:core for null-checking interop with other tools
compileOnly "com.google.code.findbugs:jsr305:3.0.2"
compileOnly project(':libs:elasticsearch-logging')
compileOnly project(':libs:logging')
testImplementation "com.carrotsearch.randomizedtesting:randomizedtesting-runner:${versions.randomizedrunner}"
testImplementation "junit:junit:${versions.junit}"
testImplementation "org.hamcrest:hamcrest:${versions.hamcrest}"
testImplementation(project(":test:framework")) {
exclude group: 'org.elasticsearch', module: 'elasticsearch-core'
exclude group: 'org.elasticsearch', module: 'core'
}
}
tasks.named('forbiddenApisMain').configure {
// :libs:elasticsearch-core does not depend on server
// :libs:core does not depend on server
// TODO: Need to decide how we want to handle for forbidden signatures with the changes to server
replaceSignatureFiles 'jdk-signatures'
}