Skip to content

Publish Java bindings that depend on a version range - #50

Merged
itvi-1234 merged 1 commit into
runtimeconditions:mainfrom
itvi-1234:maven-version-ranges
Nov 18, 2026
Merged

itvi-1234 merged 1 commit into
runtimeconditions:mainfrom
itvi-1234:maven-version-ranges

Conversation

@itvi-1234

Copy link
Copy Markdown
Member

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.

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.
@itvi-1234
itvi-1234 merged commit e73094c into runtimeconditions:main Nov 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant