Repository navigation
Fix JitPack builds and Gradle-version-dependent buildSrc imports - #634
Merged
Saloed merged 1 commit intoNov 1, 2026
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dolmatovDan
force-pushed
the
fix/jitpack-and-buildsrc-accessors
branch
from
November 1, 2026 10:25
784a70d to
64b6acd
Compare
Saloed
approved these changes
Nov 1, 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.
JitPack currently fails to build recent commits. Its default command runs
assemble, which pulls in thedistZip/distTar/startScriptstasks ofusvm-ts-fast-checkandusvm-ts-calls; these depend onbuildFastCheckAdapter, which runsnpm ciandnpm run build. The JitPack image has nonpm, so the build stops withA problem occurred starting process 'command 'npm''before any artifact is published. Neither TS module has a Maven publication, soassembleis not needed to publish anything.Add an
installcommand tojitpack.ymlthat keeps the default group/version arguments and runs only-xtest publishToMavenLocal. The JDK setting is unchanged.Three
buildSrcfiles (DetektConfiguration.kt,usvmpython/tasks/JNIHeaderTask.kt,usvmpython/tasks/PythonSamplesTasks.kt) import Kotlin DSL accessors from the generated packagegradle.kotlin.dsl.accessors._466a692754d3da37fc853e1c7ad8ae1e. The hash in that name depends on the Gradle version and the applied plugins, so compilingbuildSrcwith another Gradle version (for example, when usvm is used as an included build) fails withUnresolved reference '_466a...'. Replace these accessors with the equivalent public API:extensions.configure<DetektExtension>,extensions.getByType<DetektExtension>().toolVersion,dependencies.add("detektPlugins", ...)andextensions.getByType<SourceSetContainer>().getByName("main"/"test"). Build behavior is unchanged.Validation:
BUILD SUCCESSFUL, 13 published artifacts includingusvm-coreandusvm-util); the log contains nonpminvocation../gradlew -m -xtest publishToMavenLocalplans 130 tasks with no fast-check adapter tasks, while the currentassemble publishToMavenLocalplans 245 tasks includinginstallFastCheckAdapterandbuildFastCheckAdapter. Both publish the same 13 publications.detektPluginsresolves todetekt-formatting:1.23.5for:usvm-core, and additionally toproject :usvm-detekt-rulesfor:usvm-ts.:usvm-ts:detektreports the same 217 weighted issues onmainand on this branch.buildSrcfails to compile onmainand compiles on this branch.The Python tasks that use
sourceSetswere compiled and configured but not executed, since they require a CPython build. This PR does not make usvm build on Gradle 9: configuration then fails inusvm-jvm/build.gradle.kts(resolvedConfiguration.files), which is a separate migration.🤖 Generated with Claude Code