Re-add origin url information to publish POM files#55171
Merged
mark-vieira merged 3 commits intoelastic:masterfrom Apr 14, 2020
Merged
Re-add origin url information to publish POM files#55171mark-vieira merged 3 commits intoelastic:masterfrom
mark-vieira merged 3 commits intoelastic:masterfrom
Conversation
Collaborator
|
Pinging @elastic/es-core-infra (:Core/Infra/Build) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Some unintentional fallout from #54611 was that we lost some of the SCM information we add to our generated POM files. Turns out, this is required in order to publish artifacts to Maven Central, which has caused the most recent release to fail. This PR removes the use of the nebula plugin, and instead adds this logic to our
BuildPlugin.