Oliver Kopp
07/11/2025, 3:28 PMStarting process 'command 'C:\Users\WDAGUtilityAccount\.gradle\jdks\amazon_com_inc_-24-amd64-windows.2\bin\java.exe''. Working directory: C:\Users\WDAGUtilityAccount\AppData\Local\Temp\jabref\jabgui Command: C:\Users\WDAGUtilityAccount\.gradle\jdks\amazon_com_inc_-24-amd64-windows.2\bin\java.exe --enable-native-access=ai.djl.tokenizers,ai.djl.pytorch_engine,com.sun.jna,javafx.graphics,javafx.media,javafx.web,org.apache.lucene.core --add-opens java.base/java.nio=<http://org.apache.pdfbox.io|org.apache.pdfbox.io> --add-opens java.base/jdk.internal.ref=<http://org.apache.pdfbox.io|org.apache.pdfbox.io> --add-modules jdk.incubator.vector -XX:+UnlockExperimentalVMOptions -XX:+UseCompactObjectHeaders -XX:+UseZGC -XX:+ZUncommit -XX:+UseStringDeduplication -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -ea -cp C:\Users\WDAGUtilityAccount\.gradle\.tmp\gradle-javaexec-classpath17673669193172587711.jar --module org.jabref/org.jabref.Launcher
Successfully started process 'command 'C:\Users\WDAGUtilityAccount\.gradle\jdks\amazon_com_inc_-24-amd64-windows.2\bin\java.exe''
Then I get
Error occurred during initialization of boot layer
java.lang.module.FindException: Module org.jabref not found
Build 00ba7384-9696-4fa9-9223-172669a8483f is closed
On my Windows 10 machine (no Sandbox), gradle does not call Shortening Java classpath
.
Can I turn off this feature? Or maybe use it for module-path?Oliver Kopp
07/11/2025, 3:51 PMBen Berman
07/11/2025, 6:06 PMIvan CLOVIS Canet
07/13/2025, 8:24 AM@get:InputFile
abstract val file: RegularFileProperty
then Gradle tracks its state, which doesn't make sense since the file doesn't exist yet.
I've seen
@get:Input
abstract val file: Property<String>
used, which does work, but that's not nice to use when configuring a task.Kelvin Chung
07/14/2025, 1:10 PMval jacocoJvmTestReport by tasks.registering(JacocoReport::class) {
sourceDirectories.from(kotlin.sourceSets.commonMain.map { it.kotlin })
sourceDirectories.from(kotlin.sourceSets.jvmMain.map { it.kotlin })
}
However, the generated report can't seem to find the jvmMain
sources, only the commonMain
sources. Any idea on why that could be?Ishan Sharma
07/15/2025, 2:38 AMProcess 'command 'C:\Users\UserName\.jdks\openjdk-24.0.1\bin\java.exe'' finished with non-zero exit value 1would anyone have any idea why this is happening? Why does it give this error but when I run the file normally, it works?
Anwar Parker
07/15/2025, 7:04 AMAnwar Parker
07/15/2025, 7:05 AMAnwar Parker
07/15/2025, 7:05 AM> Timeout waiting to lock Compressed Files Expansion Cache (/var/jenkins/workspace/core/.gradle/8.14.3/expanded). It is currently in use by another Gradle instance.
Owner PID: 4814
Our PID: 3262
Owner Operation:
Our operation:
Lock file: /var/jenkins/workspace/core/.gradle/8.14.3/expanded/expanded.lock
Ice Man
07/15/2025, 8:48 AMA problem occurred configuring project ':gradle-plugin'.> A build operation failed. Could not move temporary workspace (C:\Users\HP\.gradle\caches\8.13\transforms\4515da6671b69fb128505938dbdb32ed-381b8acb-5c26-4710-b485-708106405f2e) to immutable location (C:\Users\HP\.gradle\caches\8.13\transforms\4515da6671b69fb128505938dbdb32ed) > Could not move temporary workspace (C:\Users\HP\.gradle\caches\8.13\transforms\4515da6671b69fb128505938dbdb32ed-381b8acb-5c26-4710-b485-708106405f2e) to immutable location (C:\Users\HP\.gradle\caches\8.13\transforms\4515da6671b69fb128505938dbdb32ed) does anyone know how to fix it i am stuck ;//
Jan
07/15/2025, 11:04 AMFileNotFoundException
for $HOME/.gradle/wrapper/dists/gradle-8.11.1-bin/xxxxx/gradle-8.11.1-bin.zip
and when I look into that folder there's only a .lck
and .part
files. I can actually download the ZIP in the browser, so access isn't entirely blocked.melix
07/17/2025, 1:31 PMScott Palmer
07/17/2025, 3:17 PMplugins {
id("org.gradle.toolchains.foojay-resolver-convention") version "1.0.0"
id("dev.panuszewski.typesafe-conventions") version "0.7.3"
}
./build-logic/build.gradle.kts:
plugins {
`kotlin-dsl`
}
kotlin {
jvmToolchain(21)
}
repositories {
mavenCentral()
gradlePluginPortal()
}
dependencies {
implementation(libs.commons.lang3)
}
./settings.gradle:
plugins {
id 'org.gradle.toolchains.foojay-resolver-convention' version '1.0.0'
}
// This is to propagate the backendPlatformVersion property to the build-logic convention plugin
gradle.beforeProject { project ->
if (project.hasProperty('backendPlatformVersion')) {
System.setProperty('backendPlatformVersion', project.backendPlatformVersion)
}
}
rootProject.name = 'main-project'
includeBuild("build-logic")
include 'sub-project-1'
include 'sub-project-2
include 'sub-project-3'
When I build with JAVA_HOME pointing to JDK 17:
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring project ':sub-project-1'.
> Could not resolve all dependencies for configuration 'classpath'.
> Could not resolve project :build-logic.
Required by:
project :sub-project-1
> Dependency requires at least JVM runtime version 21. This build uses a Java 17 JVM.
Shouldn't the resolver plugin cause the build to use JDK 21?Mike Wacker
07/17/2025, 11:42 PM~/.gradle/gradle.properties
(e.g., in-memory GPG key)?Slackbot
07/18/2025, 4:39 AMSimon Marquis
07/18/2025, 11:42 AMbuild-logic
directory which contains convention plugins that is add to the main build with
pluginManagement {
includeBuild("build-logic")
}
Everything works great, until I add a settings plugin (Plugin<Settings>
) that I try to apply on the main build.
The plugin is correctly applied since we can see the generated log, but the build fails right after, with a weird message about corrupted cache:
* What went wrong:
An exception occurred applying plugin request [id: 'nowinandroid.android.application']
> Failed to apply plugin 'nowinandroid.android.lint'.
> Type com.android.build.api.dsl.ApplicationExtension not present
....
....
Caused by: java.lang.TypeNotPresentException: Type com.android.build.api.dsl.ApplicationExtension not present
at org.gradle.api.reflect.TypeOf.captureTypeArgument(TypeOf.java:299)
at org.gradle.api.reflect.TypeOf.<init>(TypeOf.java:96)
at AndroidLintConventionPlugin$apply$lambda$0$$inlined$configure$1.<init>(TypeOfExtensions.kt:28)
at AndroidLintConventionPlugin.apply(AndroidLintConventionPlugin.kt:52)
at AndroidLintConventionPlugin.apply(AndroidLintConventionPlugin.kt:25)
at org.gradle.api.internal.plugins.ImperativeOnlyPluginTarget.applyImperative(ImperativeOnlyPluginTarget.java:55)
at org.gradle.api.internal.plugins.RuleBasedPluginTarget.applyImperative(RuleBasedPluginTarget.java:51)
at org.gradle.api.internal.plugins.DefaultPluginManager.addPlugin(DefaultPluginManager.java:190)
at org.gradle.api.internal.plugins.DefaultPluginManager.access$100(DefaultPluginManager.java:54)
....
....
Caused by: java.lang.ClassNotFoundException: com.android.build.api.dsl.ApplicationExtension
at org.gradle.internal.classloader.VisitableURLClassLoader$InstrumentingVisitableURLClassLoader.findClass(VisitableURLClassLoader.java:187)
(I can share the full stacktrace if needed)
Here is the corresponding code: https://github.com/android/nowinandroid/pull/1908/filesVladimir Sitnikov
07/20/2025, 6:23 AM:core
and :lib
, and :test-fixtures
. Imagine I want publishing a platform that would align the versions of :core
and :lib
. I do not publish :test-fixtures
and I use it for testing only, so I do not want including it to the bom.
Of course, I can list :bom
dependencies manually, however, it would be prone to errors as I might forget adding a module to the bom when adding a new module.
I use convention plugins to configure the publication for :core
and :lib
modules, so I would like to configure :bom
automatically for all the published projects. Can I somehow do that?
I see JUnit uses rootProject.extra
for storing the list of projects in a bom, however, it looks like it duplicates the configuration:
• firstly, it list the projects in root project extra
• secondly, the relevant subprojects have their publication configurations
The configurations could deviate. For example, a new module could be added without updating root project extra.
Is rootProject.extra
the best we can have for now? Is it safe for configuration-cache/isolated-projects?Ahmed Hasan
07/20/2025, 8:21 AMSamuel Franklin
07/21/2025, 8:35 PMWai Han
07/22/2025, 1:59 AMConfiguration on demand is an incubating feature.
> Configure project :vector-app
WARNING:BuildType(nightly): resValue 'launcher_background' value is being replaced.
WARNING:API 'ApkVariantOutput.getVersionCodeOverride()' is obsolete and has been replaced with 'VariantOutput.versionCode()'.
It will be removed in version 7.0 of the Android Gradle plugin.
Gradle Properties must be used to change Variant information.
For more information, see <https://d.android.com/r/tools/use-properties>.
To determine what is calling ApkVariantOutput.getVersionCodeOverride(), use -Pandroid.debug.obsoleteApi=true on the command line to display more information.
ABI arm64-v8a -> VersionCode = 40104362
ABI armeabi-v7a -> VersionCode = 40104361
ABI null -> VersionCode = 40104360
ABI x86 -> VersionCode = 40104363
ABI x86_64 -> VersionCode = 40104364
ABI arm64-v8a -> VersionCode = 40104362
ABI armeabi-v7a -> VersionCode = 40104361
ABI null -> VersionCode = 40104360
ABI x86 -> VersionCode = 40104363
ABI x86_64 -> VersionCode = 40104364
ABI arm64-v8a -> VersionCode = 40104362
ABI armeabi-v7a -> VersionCode = 40104361
ABI null -> VersionCode = 40104360
ABI x86 -> VersionCode = 40104363
ABI x86_64 -> VersionCode = 40104364
ABI arm64-v8a -> VersionCode = 40104362
ABI armeabi-v7a -> VersionCode = 40104361
ABI null -> VersionCode = 40104360
ABI x86 -> VersionCode = 40104363
ABI x86_64 -> VersionCode = 40104364
ABI arm64-v8a -> VersionCode = 40104362
ABI armeabi-v7a -> VersionCode = 40104361
ABI null -> VersionCode = 40104360
ABI x86 -> VersionCode = 40104363
ABI x86_64 -> VersionCode = 40104364
ABI arm64-v8a -> VersionCode = 40104362
ABI armeabi-v7a -> VersionCode = 40104361
ABI null -> VersionCode = 40104360
ABI x86 -> VersionCode = 40104363
ABI x86_64 -> VersionCode = 40104364
FAILURE: Build failed with an exception.
* What went wrong:
Could not determine the dependencies of task ':matrix-sdk-android:javaPreCompileDebug'.
> Could not resolve all task dependencies for configuration ':matrix-sdk-android:_agp_internal_javaPreCompileDebug_kaptClasspath'.
> Could not find dk.ilios:realmfieldnameshelper:2.0.0.
Required by:
project :matrix-sdk-android
* Try:
> Run with *--stacktrace* option to get the stack trace.
Run with* Get more help at*--info* or *--debug* option to get more log output.
<https://help.gradle.org>
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See <https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings>
*BUILD FAILED* in 6s
Martin
07/22/2025, 4:33 PMsettings.gradle.kts
buildscript classpath? I've tried this but it doesn't work:
pluginManagement {
includeBuild("my-build")
}
buildscript {
dependencies {
// com.example:artifact-id is built by the `my-build` included build
// I was expecting dependency substitution to happen here but it doesn't look like it's the case?
classpath("com.example:artifact-id")
}
}
Is there a way?Kelvin Chung
07/22/2025, 9:08 PMClayton Walker
07/23/2025, 4:28 PMGábor Török
07/25/2025, 5:02 PM2025-07-24T19:17:24.388-0700 [INFO] [org.gradle.api.internal.tasks.compile.incremental.SelectiveCompiler] Full recompilation is required because JdkClassWriter.class could not be analyzed for incremental compilation. See the debug log for more details. Analysis took 1.717 secs.
the problem is that this is our biggest project, and the full compilation can take up to more than a minute - which slows down iterating on problems A LOT.
• enabling the debug log does not seem to give me any more detailed information.
• JdkClassWriter.class
is only present in dependencies that are also present in other projects that do not have this problem..Jerome Haltom
07/25/2025, 5:14 PMCaleb Cushing
07/29/2025, 1:14 AMAndrzej Zabost
07/30/2025, 12:16 PMbuildscript
block is used or not (or, at least, that seems to be the difference).
I'm sharing the post from #CJYS1DAP5 for visibility because I assume the problem may be more generic and not necessarily Android related.
https://gradle-community.slack.com/archives/CJYS1DAP5/p1753877427121339Jacob Tindi
07/30/2025, 2:31 PMJacob Tindi
07/30/2025, 2:33 PMColton Idle
07/30/2025, 5:56 PM