fantastic Dev
04/25/2025, 4:41 PM% ./gradle
Error occurred during initialization of VM
Could not resolve "ZIP_Open": /Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home/lib/libzip.dylib
Eli Graber
04/25/2025, 4:45 PMjava.lang.System::load
warnings with Gradle 8.14 and Java 24? I would think not because of #31625, but not sure.Eli Graber
04/25/2025, 5:24 PM--enable-native-access=ALL-UNNAMED
to my jvm args until all of these libraries/tools migrate off of JNI (so probably never)?
WARNING: A restricted method in java.lang.System has been called
WARNING: java.lang.System::load has been called by com.android.layoutlib.bridge.Bridge in an unnamed module (file:/home/eli/.gradle/caches/8.14/transforms/7ddbbeceffb506f2342ae2f7da76cf06/transformed/layoutlib-15.1.4.jar)
WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for callers in this module
WARNING: Restricted methods will be blocked in a future release unless native access is enabled
Sebastian Schuberth
04/27/2025, 8:11 AMBob Shalom
04/27/2025, 8:17 AMVladimir Sitnikov
04/28/2025, 7:22 AMConfigurableFileCollection
vs ListProperty<RegularFile>
Is there anything like āprefer ConfigurableFileCollection
in newer codeā or āprefer ListProperty<RegularFile>
in newer codeā ?
I assume the answer should be the same for both task properties and extension properties, however, it would be great to learn if thereās a difference.Giuseppe Barbieri
04/28/2025, 12:20 PMorg.jogamp.gluegen:gluegen-rt
and the natives as variants
now I'm on the consumer side, with a test project, expanding the runtime configuration for each variant, adding the corresponding file underneath, but Gradle complains:
Could not resolve org.jogamp.gluegen:gluegen-rt:0.0.8 for variant-tester:main
Could not resolve org.jogamp.gluegen:gluegen-rt:0.0.8 for variant-tester:test
hissam ud din
04/29/2025, 12:58 AMA problem occurred configuring project ':gradle'.> Multiple build operations failed. Could not isolate parameters org.gradle.api.internal.initialization.transform.MergeInstrumentationAnalysisTransform$Parameters_Decorated@50814c83 of artifact transform MergeInstrumentationAnalysisTransform Could not isolate parameters org.gradle.api.internal.initialization.transform.MergeInstrumentationAnalysisTransform$Parameters_Decorated@50814c83 of artifact transform MergeInstrumentationAnalysisTransform Could not isolate parameters org.gradle.api.internal.initialization.transform.MergeInstrumentationAnalysisTransform$Parameters_Decorated@50814c83 of artifact transform MergeInstrumentationAnalysisTransform Could not isolate parameters org.gradle.api.internal.initialization.transform.MergeInstrumentationAnalysisTransform$Parameters_Decorated@50814c83 of artifact transform MergeInstrumentationAnalysisTransform Could not isolate parameters org.gradle.api.internal.initialization.transform.MergeInstrumentationAnalysisTransform$Parameters_Decorated@50814c83 of artifact transform MergeInstrumentationAnalysisTransform Could not isolate parameters org.gradle.api.internal.initialization.transform.MergeInstrumentationAnalysisTransform$Parameters_Decorated@50814c83 of artifact transform MergeInstrumentationAnalysisTransform Could not isolate parameters org.gradle.api.internal.initialization.transform.MergeInstrumentationAnalysisTransform$Parameters_Decorated@50814c83 of artifact transform MergeInstrumentationAnalysisTransform Could not isolate parameters org.gradle.api.internal.initialization.transform.MergeInstrumentationAnalysisTransform$Parameters_Decorated@50814c83 of artifact transform MergeInstrumentationAnalysisTransform Could not isolate parameters org.gradle.api.internal.initialization.transform.MergeInstrumentationAnalysisTransform$Parameters_Decorated@50814c83 of artifact transform MergeInstrumentationAnalysisTransform Could not isolate parameters org.gradle.api.internal.initialization.transform.MergeInstrumentationAnalysisTransform$Parameters_Decorated@50814c83 of artifact transform MergeInstrumentationAnalysisTransform ...and 20 more failures. > Could not isolate parameters org.gradle.api.internal.initialization.transform.MergeInstrumentationAnalysisTransform$Parameters_Decorated@50814c83 of artifact transform MergeInstrumentationAnalysisTransform > Could not isolate value org.gradle.api.internal.initialization.transform.MergeInstrumentationAnalysisTransform$Parameters_Decorated@50814c83 of type MergeInstrumentationAnalysisTransform.Parameters > Multiple build operations failed. Could not move temporary workspace (C:\Users\dell\.gradle\caches\8.10.2\transforms\904c97b439784601ff0eee25e3c43bac-84c63b27-7c61-4f8e-b3c9-ac04c14f9c94) to immutable location (C:\Users\dell\.gradle\caches\8.10.2\transforms\904c97b439784601ff0eee25e3c43bac) Could not move temporary workspace (C:\Users\dell\.gradle\caches\8.10.2\transforms\4c75e264bb05f340dad2540f720bcb1b-9fc2d5c5-fbc6-4b93-8074-75ef4d405d09) to immutable location (C:\Users\dell\.gradle\caches\8.10.2\transforms\4c75e264bb05f340dad2540f720bcb1b) > Could not move temporary workspace (C:\Users\dell\.gradle\caches\8.10.2\transforms\904c97b439784601ff0eee25e3c43bac-84c63b27-7c61-4f8e-b3c9-ac04c14f9c94) to immutable location (C:\Users\dell\.gradle\caches\8.10.2\transforms\904c97b439784601ff0eee25e3c43bac) > Could not move temporary workspace (C:\Users\dell\.gradle\caches\8.10.2\transforms\4c75e264bb05f340dad2540f720bcb1b-9fc2d5c5-fbc6-4b93-8074-75ef4d405d09) to immutable location (C:\Users\dell\.gradle\caches\8.10.2\transforms\4c75e264bb05f340dad2540f720bcb1b) * Try:
Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.BUILD FAILED in 1m 38s Error: Gradle task assembleDebug failed with exit code 1
Kaan Avdan
04/29/2025, 8:27 AMKen Yee
04/29/2025, 7:18 PMtasks.register("updateModuleCapabilitiesIndex") {
val watchFiles = fileTree(project.rootDir) {
include("**/build.gradle", "**/build.gradle.kts")
}.files
val moduleIndexFile = "${layout.buildDirectory.get()}/moduleCapabilities.json"
val moduleIndexCmdLine = listOf(
"./gradlew",
"...",
)
inputs.files(watchFiles)
doLast {
providers.exec {
commandLine = moduleIndexCmdLine
}
}
dependsOn("build")
}
Command removed for simplification, but I'm trying to write something that parses the gradle files and then saves the info into another file in a cacheable way.
The doLast{...} bit unfortunately contains a gradle script which is not serializable... Tried to search in this slack but configuration cache gets a lot of unrelated hits šSettingDust
04/30/2025, 3:13 AMCircular dependency between the following tasks:
work action Dependencies for XXXXXX
? Looks like the transform action depends on each other?
The image is the cycle shows in debugger. Looks like the states of different transform is looping. How can I avoid that?
https://github.com/SettingDust/cloche/blob/feature/extract-includes/src/main/kotlin/earth/terrarium/cloche/target/TargetCompilation.kt#L122-L148
Circular dependency between the following tasks:
work action Dependencies for dev.su5ed.sinytra.fabric-api:fabric-api-deprecated:0.92.2+1.11.11+1.20.1 {earth.terrarium.cloche.modState=none}
Rochana Prabasara
04/30/2025, 6:46 AMEmil Kantis
04/30/2025, 8:30 AMHadi
05/01/2025, 10:57 PMEntry META-INF/gradle.kotlin_module is a duplicate but no duplicate handling strategy has been set. Please refer to https://docs.gradle.org/8.10.2/dsl/org.gradle.api.tasks.Copy.html#org.gradle.api.tasks.Copy:duplicatesStrategy for details.* Try:
Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.BUILD FAILED in 491ms Running Gradle task 'assembleRelease'... 583ms Gradle task assembleRelease failed with exit code 1
Stephen Muendo
05/02/2025, 9:21 AMA problem occurred configuring project ':gradle'.> Could not resolve all artifacts for configuration 'Gclasspath'. > Failed to transform kotlin-compiler-embeddable-1.9.24.jar (org.jetbrains.kotlinkotlin compiler embeddable1.9.24) to match attributes {artifactType=jar, org.gradle.category=library, org.gradle.internal.instrumented=instrumented-and-upgraded, org.gradle.libraryelements=jar, org.gradle.status=release, org.gradle.usage=java-runtime}. > Execution failed for ExternalDependencyInstrumentingArtifactTransform: C:\Users\STEVE\.gradle\caches\8.10.2\transforms\9478a9a76c123b2f65189f158657fc62\transformed\merge\instrumentation-dependencies.bin. > java.lang.IllegalStateException: Could not serialize types map to a file: C:\Users\STEVE\.gradle\caches\8.10.2\transforms\9478a9a76c123b2f65189f158657fc62\transformed\merge\instrumentation-dependencies.bin * Try:
Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.BUILD FAILED in 2s Error: Gradle task assembleDebug failed with exit code 1
Muhammad Moeen
05/02/2025, 4:20 PM> Task :gradle-plugin:react-native-gradle-plugin:compileJava NO-SOURCE
> Task :gradle-plugin:react-native-gradle-plugin:classes
> Task :gradle-plugin:react-native-gradle-plugin:jar
> Task :expo-dev-launcher-gradle-plugin:compileKotlin
> Task :expo-dev-launcher-gradle-plugin:compileJava NO-SOURCE
> Task :expo-dev-launcher-gradle-plugin:classes
> Task :expo-dev-launcher-gradle-plugin:jar
> Configure project :app
ā¹ļø Applying gradle plugin 'expo-dev-launcher-gradle-plugin' (expo-dev-launcher@5.1.10)
FAILURE: Build completed with 2 failures.
1: Task failed with an exception.
-----------
* Where:
Build file '/home/expo/workingdir/build/node_modules/expo-clipboard/android/build.gradle' line: 3
* What went wrong:
Plugin [id: 'expo-module-gradle-plugin'] was not found in any of the following sources:
- Gradle Core Plugins (not a core plugin. For more available plugins, please refer to <https://docs.gradle.org/8.10.2/userguide/plugin_reference.html> in the Gradle documentation.)
- Included Builds (None of the included builds contain this plugin)
- Plugin Repositories (plugin dependency must include a version number for this source)
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at <https://help.gradle.org>.
==============================================================================
2: Task failed with an exception.
-----------
* Where:
Script '/home/expo/workingdir/build/node_modules/expo-modules-core/android/ExpoModulesCorePlugin.gradle' line: 95
* What went wrong:
A problem occurred configuring project ':expo'.
> Could not get unknown property 'release' for SoftwareComponent container of type org.gradle.api.internal.component.DefaultSoftwareComponentContainer.
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug
option to get more log output.
> Run with --scan to get full insights.
> Get more help at <https://help.gradle.org>.
==============================================================================
BUILD FAILED in 1m 35s
18 actionable tasks: 18 executed
Error: Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.
James Daugherty
05/02/2025, 11:30 PMAnthony Spencer
05/02/2025, 11:44 PMJoy
05/04/2025, 11:32 AM⯠flutter run -d emulator-5554
Launching lib/main.dart on sdk gphone64 arm64 in debug mode...
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':cf56914b32:compileKotlin'.
> java.nio.file.NoSuchFileException: /nix/store/s4n9rd6y8aiychhpylmkvpf0yh0migj9-flutter-wrapped-3.29.3-sdk-links/packages/flutter_
tools/gradle/.gradle/kotlin/sessions/kotlin-compiler-12913036745881058983.salive
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at <https://help.gradle.org>.
BUILD FAILED in 771ms
Running Gradle task 'assembleDebug'... 1,372ms
Error: Gradle task assembleDebug failed with exit code 1
I tried to redirect gradle
related path with environment path and gradle property file, but neither work:
⯠flutter run -d emulator-5554 -Porg.gradle.user.home=/Users/me/.gradle
⯠export GRADLE_USER_HOME=/Users/me/.gradle/
⯠export ANDROID_GRADLE_USER_HOME=/Users/me/.gradle/
⯠cat android/gradle.properties
gradle.user.home=/Users/me/.gradle/
android.gradle.user.home=/Users/me/.gradle/
android.overridePathCheck=true
Is it possible to redirect gradle cache path to solve this?Igor Mukhin
05/05/2025, 9:45 AMRunning command in /home/runner/work/orunext20-ucl/orunext20-ucl: [/opt/hostedtoolcache/CodeQL/2.21.2/x64/codeql/java/tools/autobuild.sh]
[2025-05-05 09:31:35] [build-stderr] Picked up JAVA_TOOL_OPTIONS: -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false
[2025-05-05 09:31:36] [build-stdout] [2025-05-05 09:31:36] Build directory is /home/runner/work/orunext20-ucl/orunext20-ucl/.
[2025-05-05 09:31:36] [build-stdout] [2025-05-05 09:31:36] Found no Java toolchains in a toolchains file, inspecting environment variables...
[2025-05-05 09:31:36] [build-stdout] [2025-05-05 09:31:36] Discovered Java toolchain for version 11.0.0 at /usr/lib/jvm/temurin-11-jdk-amd64 in JAVA_HOME_11_X64
[2025-05-05 09:31:36] [build-stdout] [2025-05-05 09:31:36] Discovered Java toolchain for version 8.0.0 at /usr/lib/jvm/temurin-8-jdk-amd64 in JAVA_HOME_8_X64
[2025-05-05 09:31:36] [build-stdout] [2025-05-05 09:31:36] Discovered Java toolchain for version 17.0.0 at /usr/lib/jvm/temurin-17-jdk-amd64 in JAVA_HOME_17_X64
[2025-05-05 09:31:36] [build-stdout] [2025-05-05 09:31:36] Discovered Java toolchain for version 21.0.0 at /usr/lib/jvm/temurin-21-jdk-amd64 in JAVA_HOME_21_X64
[2025-05-05 09:31:36] [build-stdout] [2025-05-05 09:31:36] Found no Java toolchains in a toolchains file, inspecting environment variables...
[2025-05-05 09:31:36] [build-stdout] [2025-05-05 09:31:36] Discovered Java toolchain for version 11.0.0 at /usr/lib/jvm/temurin-11-jdk-amd64 in JAVA_HOME_11_X64
[2025-05-05 09:31:36] [build-stdout] [2025-05-05 09:31:36] Discovered Java toolchain for version 8.0.0 at /usr/lib/jvm/temurin-8-jdk-amd64 in JAVA_HOME_8_X64
[2025-05-05 09:31:36] [build-stdout] [2025-05-05 09:31:36] Discovered Java toolchain for version 17.0.0 at /usr/lib/jvm/temurin-17-jdk-amd64 in JAVA_HOME_17_X64
[2025-05-05 09:31:36] [build-stdout] [2025-05-05 09:31:36] Discovered Java toolchain for version 21.0.0 at /usr/lib/jvm/temurin-21-jdk-amd64 in JAVA_HOME_21_X64
[2025-05-05 09:31:36] [build-stdout] [2025-05-05 09:31:36] Identified 11.0.27 as the newest version of Java supported by the version of Gradle in use. The system default of 11.0.27 is compatible with this.
[2025-05-05 09:31:36] [build-stdout] [2025-05-05 09:31:36] [autobuild] > ./gradlew --no-daemon -S -Dorg.gradle.dependency.verification=off -Dorg.gradle.warning.mode=none --init-script "/tmp/semmleTempDir15082949693635508564/init.gradle" clean
[2025-05-05 09:31:36] [build-stdout] [2025-05-05 09:31:36] [autobuild] Picked up JAVA_TOOL_OPTIONS: -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false
[2025-05-05 09:31:37] [build-stdout] [2025-05-05 09:31:37] [autobuild] Downloading <https://services.gradle.org/distributions/gradle-8.13-bin.zip>
[2025-05-05 09:31:39] [build-stdout] [2025-05-05 09:31:39] [autobuild] .............10%.............20%.............30%.............40%.............50%.............60%.............70%.............80%.............90%.............100%
[2025-05-05 09:31:40] [build-stdout] [2025-05-05 09:31:40] [autobuild] Welcome to Gradle 8.13!
My build uses Gradle 8.13 and requires at least JVM 17 (some of plugins requires JVM 17). Do you have any idea why it picks up JVM 11?
See log: Identified 11.0.27 as the newest version of Java supported by the version of Gradle in use. The system default of 11.0.27 is compatible with this.
Adam
05/05/2025, 11:35 AMorg.jetbrains.kotlin:kotlin-native-prebuilt
(which is simple - just pick the right OS-Arch variant, download and unpack), and the also the required dependencies (which is more complicated).
Each kotlin-native-prebuilt
archive contains a konan.properties
file, that (among other things), can be processed to produce the URLs of required dependencies per Kotlin Native target, e.g. <https://download.jetbrains.com/kotlin/native/resources/llvm/16.0.0-aarch64-macos/llvm-16.0.0-aarch64-macos-dev-63.tar.gz>
.
The current download dependencies utility (org.jetbrains.kotlin:kotlin-native-utils
) is slow, doesn't cache downloads, and is hard to customise.
Options:
⢠I see ComponentMetadataRules can add variants, and the variant can have custom files, and the URLs of the files can be explicitly specified. However, a CMR can't read files, so I can't see how to compute the dependencies from konan.properties
.
⢠Maybe it's possible to compute the necessary files in prior step and add them as arguments to the CMR? But I don't think that would be possible - the phases are out of order.
⢠I want to avoid Artifact Transforms because they're too sensitive to classpath changes. Re-running when there's any change would be very slow.Giuseppe Barbieri
05/06/2025, 3:03 PM.module
file, I cant find any jogl dependency for apiElements
and I don't understand whyPhilip W
05/06/2025, 6:05 PMtesting.suites.named("test", JvmTestSuite); testing.suites.create("TEST", JvmTestSuite)
tony
05/06/2025, 10:31 PMComponentMetadataRule
is the best way to solve it but I can't quite get it to work.
I have a repo publishing a module using Bazel (and a pom file for the metadata) and that module has a dependency on something published from another repo that uses Gradle. The dependency is a test fixture (modeled in Gradle as you'd expect). I have a third module that depends on the Bazel-published module; this third module uses Gradle. Gradle is not able to resolve the transitive test-fixture dependency, failing with an `ArtifactNotFoundException`: it's looking for name-test-fixtures.jar
when it really ought to be looking for name-version-test-fixtures.jar
.
My rule looks like this so far:
class MyRule : ComponentMetadataRule {
override fun execute(context: ComponentMetadataContext) {
context.details.allVariants {
withDependencies {
removeAll { it.module.toString() == "com.squareup.misk:misk-vitess" }
//add("???") // what to add?
}
}
}
now, if I leave it as-is, it happens that compilation succeeds because the test-fixtures module for compilation is also coming into the graph via another path. But this isn't guaranteed so I want to fix this metadata so that compilation will always succeed. But I'm not sure how to re-add the test-fixture variant. In a dependencies block, it would look like testImplementation(testFixtures("com.squareup.misk:misk-vitess:1"))
, but I don't know how to express that (specifically the testFixtures()
part) in the add(...)
method.Leon Abire
05/07/2025, 5:22 AMLeon Abire
05/07/2025, 5:22 AMplatforms: linux:
default_package: open_filex
or add an inline implementation to open_filex via platforms: linux:
pluginClass
or`dartPluginClass`.
Package open_filex:macos references open_filex:macos as the default plugin, but it does not provide an inline
implementation.
Ask the maintainers of open_filex to either avoid referencing a default implementation via platforms: macos:
default_package: open_filex
or add an inline implementation to open_filex via platforms: macos:
pluginClass
or`dartPluginClass`.
Package open_filex:windows references open_filex:windows as the default plugin, but it does not provide an inline
implementation.
Ask the maintainers of open_filex to either avoid referencing a default implementation via platforms: windows:
default_package: open_filex
or add an inline implementation to open_filex via platforms: windows:
pluginClass
or dartPluginClass
.
Package open_filex:linux references open_filex:linux as the default plugin, but it does not provide an inline
implementation.
Ask the maintainers of open_filex to either avoid referencing a default implementation via platforms: linux:
default_package: open_filex
or add an inline implementation to open_filex via platforms: linux:
pluginClass
or`dartPluginClass`.
Package open_filex:macos references open_filex:macos as the default plugin, but it does not provide an inline
implementation.
Ask the maintainers of open_filex to either avoid referencing a default implementation via platforms: macos:
default_package: open_filex
or add an inline implementation to open_filex via platforms: macos:
pluginClass
or`dartPluginClass`.
Package open_filex:windows references open_filex:windows as the default plugin, but it does not provide an inline
implementation.
Ask the maintainers of open_filex to either avoid referencing a default implementation via platforms: windows:
default_package: open_filex
or add an inline implementation to open_filex via platforms: windows:
pluginClass
or dartPluginClass
.
Package open_filex:linux references open_filex:linux as the default plugin, but it does not provide an inline
implementation.
Ask the maintainers of open_filex to either avoid referencing a default implementation via platforms: linux:
default_package: open_filex
or add an inline implementation to open_filex via platforms: linux:
pluginClass
or`dartPluginClass`.
Package open_filex:macos references open_filex:macos as the default plugin, but it does not provide an inline
implementation.
Ask the maintainers of open_filex to either avoid referencing a default implementation via platforms: macos:
default_package: open_filex
or add an inline implementation to open_filex via platforms: macos:
pluginClass
or`dartPluginClass`.
Package open_filex:windows references open_filex:windows as the default plugin, but it does not provide an inline
implementation.
Ask the maintainers of open_filex to either avoid referencing a default implementation via platforms: windows:
default_package: open_filex
or add an inline implementation to open_filex via platforms: windows:
pluginClass
or dartPluginClass
.
FAILURE: Build failed with an exception.
* Where:
Settings file 'C:\Users\USER\Videos\Mobile-app-customer\android\settings.gradle' line: 15
* What went wrong:
Plugin [id: 'dev.flutter.flutter-gradle-plugin', version: '1.0.0'] was not found in any of the following sources:
- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Plugin Repositories (could not resolve plugin artifact 'dev.flutter.flutter-gradle-plugindev.flutter.flutter gradle plugin.gradle.plugin1.0.0')
Searched in the following repositories:
Google
MavenRepo
Gradle Central Plugin Repository
maven(https://storage.googleapis.com/download.flutter.io)
* Try:
Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.BUILD FAILED in 1m 8s Running Gradle task 'assembleRelease'... 70.7s Gradle task assembleRelease failed with exit code 1
Leon Abire
05/07/2025, 5:23 AMSlackbot
05/07/2025, 5:23 AMSreenivas
05/07/2025, 6:17 AMgradle build -x shadowJar
but it will be really helpful to disable the default configuration in shadowJar plugin..Philip W
05/07/2025, 11:01 AM