Repository navigation
Publish Java bindings that depend on a version range - #50
Merged
Merged
Conversation
The generated poms depend on the first-party bindings with a range, such as [0.1.0,0.2.0). The publication script looked that up as if it were a file name, so it never found the dependency on Maven Central and refused to upload any package that has one, and it did not order a package after the selected one that meets its range. Match a range against the versions Maven Central lists, and order by artifact and range. Ran a dry run of common-integrations and env-configuration together on the committed poms.
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
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.
The generated poms depend on the first-party bindings with a range, such as [0.1.0,0.2.0). The publication script looked that up as if it were a file name, so it never found the dependency on Maven Central and refused to upload any package that has one, and it did not order a package after the selected one that meets its range.
Match a range against the versions Maven Central lists, and order by artifact and range. Ran a dry run of common-integrations and env-configuration together on the committed poms.