Allow scaffold to add a new version for an existing library#1666
Merged
Conversation
…lready supported library
vjovanov
approved these changes
Apr 9, 2026
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.
Summary
scaffoldto generate a new metadata/test scaffold for a fresh version of an already supportedgroupId:artifactId--forceis usedlatestentry when appending versions, including older versionsindex.jsonfiles with the repositorys multi-line pretty-print styleDetails
index.jsonentryindex.jsoninstead of failing just because the artifact root already existslatestfrom the highest metadata version after updates instead of relying on insertion orderScaffoldTaskJSON output with the formatting used by the other index update tasksTesting
../../gradlew test --tests org.graalvm.internal.tck.ScaffoldTaskTests --stacktraceFixes: #1665