-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Always use archive base name as the pom artifact id #56447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Pinging @elastic/es-core-infra (:Core/Infra/Build) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
||
// have to defer this until archivesBaseName is set | ||
project.afterEvaluate { | ||
publication.artifactId = project.convention.getPlugin(BasePluginConvention).archivesBaseName |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's unfortunate MavenPublication doesn't use Providers :/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My thoughts exactly.
We override the
archivesBaseName
for several projects. When these are published, we also interpret the GAV coordinates to use the update archive name as well. However, Gradle publishing plugins use the project name by default. We override this manually in several places but it's easy to miss some, like shadow jar projects. This PR moves this logic into ourBuildPlugin
so it's done in a central location and there no risk of forgetting to add the override.Relates to #56415