I used to be able to debug my model builder plugin by connecting to it via

connection.model(OrtDependencyTreeModel::class.java).setJvmArgumen
ts("-Dorg.gradle.debug=true").get()

I haven't tried this in a while, but now that I do again, it does not seem to work anymore; the Gradle daemon does not stop the process to wait for the remote debugger to attach. Has anything changed in Gradle 9.x in this regard?

* What went wrong: Execution failed for task 'expo modules coreconfigureCMakeDebug[arm64-v8a]'.

[CXX1214] C:\Users\uppal\Downloads\cometchat-uikit-react-native-5\FloxlyApp\node_modules\expo-modules-core\android\CMakeLists.txt debug|arm64-v8a : User has minSdkVersion 22 but library was built for 24 [//ReactAndroid/hermestooling]

can someone please tell me issue to get it fix I'm working with react-native-expo project for voipcall setup feature

What's the best way to test assertions, enforce rules, etc... for Gradle in a build with many projects? Some of the assertions might be specific to one project (e.g. this project can't depend on any other project in the build) and another might apply to all projects (e.g. all projects should be applying a specific convention plugin)

Is there a way to pass jvm args to

gradle.properties

such that if the current jvm version doesn't recognise them, they'll be ignored?

org.gradle.jvmargs=-Xmx5g -XX:+UseCompactObjectHeaders

UseCompactObjectHeaders

is only available on jvm25 and I don't want to force it on everyone in the team yet

What's the minimum required for Gradle TestKit? https://docs.gradle.org/current/userguide/test_kit.html says to just call the method

gradleTestKit()

but… I don't have it. I assume there's a specific plugin that adds it?

I want to gradle profile next - checkout latest release tag, profile non-abi change (or whatever change that will change git cleaness), and same but on the head. Can I achieve it with just scenario files? Every git operation I put in scenario - fails because looks like non abi change makes tree dirty.

We have tried to publish a plugin or plugins.gradle.org using the Plugin Publish Plugin and according to the plugin everything was done correctly. This was done a little more then one week ago and we have yet to receive any indication that the plugin has been approved. As far as I can tell we have also not received any email telling us that we have been rejected. Is there a way to confirm that the submission actually went as expected and/or check the status of the plugin (eg. Pending approval, rejected etc)?

in the latest gradle how should I add java compiler arguments considering 1. I don't know where else I might be modifying them 2. bonus points for only adding them when a given dependency is present. I noticed a providers option, but I'm also not entirely certain on the best way to handle 2.

can you pass a "bundle" to

platform

?

Hey guys ✌️ Does the configuration cache clear old entries automatically? I sometimes come into situations where it grows quite large and I need to delete it manually

Is there a configuration-cache compatible way to access

project.version

during a task action?

Trying to update to Gradle 9.4 and getting

A problem occurred configuring project ':buildSrc'.
> Could not resolve all artifacts for configuration 'classpath'.
   > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugin-api:2.2.21
 Required by:
         buildscript of project ':buildSrc' > org.jetbrains.kotlin.plugin.serialization:org.jetbrains.kotlin.plugin.serialization.gradle.plugin:2.2.21 > org.jetbrains.kotlin:kotlin-serialization:2.3.0 > org.jetbrains.kotlin:kotlin-gradle-plugins-bom:2.3.0> Unable to find a variant with the requested capability: coordinates 'org.jetbrains.kotlin:kotlin-gradle-plugin-api-gradle813':
           - Variant 'apiElementsWithFixedAttribute' provides 'org.jetbrains.kotlin:kotlin-gradle-plugin-api:2.3.0'
           - Variant 'gradle80ApiElements' provides 'org.jetbrains.kotlin:kotlin-gradle-plugin-api:2.3.0'
           - Variant 'gradle80JavadocElements' provides 'org.jetbrains.kotlin:kotlin-gradle-plugin-api:2.3.0'
           - Variant 'gradle80RuntimeElements' provides 'org.jetbrains.kotlin:kotlin-gradle-plugin-api:2.3.0'

Two questions: Transitive Dependencies: gradle now produces a warning when using

configurations { api { transtive = false } }

Publishing non-transitive configuration 'apiElements'. This behavior has been deprecated. This will fail with an error in Gradle 10. Setting 'transitive = false' at the configuration level is ignored by publishing. Consider using 'transitive = false' on each dependency if this needs to be published.

Is there a good way to configure every dependency as transitive without literally adding

{ transitive = false }

to every dependency line? I have a task that generates files used during dev/compile. Added to

sourceSets.main.java.srcDir files('src/main/generated')

Which now throws a implicit dependency issue on a bunch of tasks. Is there any simpler way then adding 20

tasks.named(sourceSets.main.getCompileTaskName('java')).configure { t -> t.mustRunAfter(generate) }

lines? Note I don't want to make generate run every invocation of gradle. Hence mustRunAfter and not dependeOn. The generated files are checked into our vcs so they don't need to be generated every run. But also tested

sourceSets.main.java.srcDir generate.flatMap { it.output }

and didn't change anything.

Gradle are deprecating the delegated properties utils, e.g.

val foo by tasks.registering

https://github.com/gradle/gradle/pull/37556 I rather like these utils. They help make buildscripts more concise. I've created an issue to restore them https://github.com/gradle/gradle/issues/37604. Does anyone have thoughts on this?

gradle 8.14.4 is causing some weird kotlin-stdlib errors for me (that 8.14.3 and 9.x don't seem to cause). Did something change with how certain these libs were included by default?

Hello everyone! When i try to build my android project, i have troubles downloading needed version. It just cancels by timeout:

Downloading <https://services.gradle.org/distributions/gradle-8.13-bin.zip>

Exception in thread "main" java.io.IOException: Downloading from https://services.gradle.org/distributions/gradle-8.13-bin.zip failed: timeout (10000ms) at org.gradle.wrapper.Install.forceFetch(SourceFile:4) at org.gradle.wrapper.Install$1.call(SourceFile:8) at org.gradle.wrapper.GradleWrapperMain.main(SourceFile:67) Caused by: java.net.SocketTimeoutException: Read timed out at java.base/sun.nio.ch.NioSocketImpl.timedRead(NioSocketImpl.java:278) at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:304) at java.base/sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:346) at java.base/sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:796) at java.base/java.net.Socket$SocketInputStream.read(Socket.java:1099) at java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:489) at java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:483) at java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160) at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111) at java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1506) at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1421) at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:455) at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:426) at java.base/sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:586) at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:187) at java.base/sun.net.www.protocol.http.HttpURLConnection.followRedirect0(HttpURLConnection.java:2939) at java.base/sun.net.www.protocol.http.HttpURLConnection.followRedirect(HttpURLConnection.java:2848) at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1959) at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1629) at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:223) at org.gradle.wrapper.Install.forceFetch(SourceFile:2) Also i can not download from here, it just hangs: https://gradle.org/releases/ Also https://github.com/gradle/gradle-distributions/releases/download/v8.13.0/gradle-8.13-bin.zip doesn't work.

Ci run

hey excuse me sorry to bother you, I have been trying gradle for a while now and i feel like there are multiple issue it is too long to discuss, but ill try my best. So while using the app intellij gradle has been nothing but completely unsupportive the entire time, either its version is too high or its version is too low then i need to change the version of the java im using and if i do gradle just shows errors again and again, I dont understand much coding but I really try my best and I tried fixing the problem by my self but 2 hours is enough. I sent images showing my situation how it keeps giving me errors and no mattor how hard i try to fix them something else gets an error

The full line is : CONFIGURE SUCCESSFUL in 3s

Configure project :

Fabric Loom: 1.16.1 FAILURE: Build failed with an exception. * Where: Build file 'C:\Users\ASUS\IdeaProjects\AutoGGX\build.gradle' line: 40 * What went wrong: A problem occurred evaluating root project 'AutoGGX'.

Could not find method modImplementation() for arguments [net.fabricmcfabric loader0.18.4] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

* 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 from a Build Scan (powered by Develocity).

Get more help at https://help.gradle.org.

CONFIGURE FAILED in 37s

I fixed this issue before (I really dont remember how) but then it just said that the version is incompatible (yes i tried refreshing gradle, yes i deleted the .gradle files for it to restart again, yes i didnt touch anything while it was loading, yes i cleared all the cache) I hope i can get a reply as soon as possible, I havent even started on my project. Im deeply sorry for any rudeness in my tone or these messages, but I really got tired and i should have came here sooner but I was trying to fix it myself.

I'm seeing plugin portal being rate limited by maven central, i.e.

13:36:05        > Could not resolve software.amazon.awssdk:ssooidc:2.40.8.
13:36:05           > Could not get resource '<https://plugins.gradle.org/m2/software/amazon/awssdk/ssooidc/2.40.8/ssooidc-2.40.8.pom>'.
13:36:05              > Could not GET '<https://repo.maven.apache.org/maven2/software/amazon/awssdk/ssooidc/2.40.8/ssooidc-2.40.8.pom>'. Received status code 429 from server: Too Many Requests

Anybody else? https://status.gradle.com/ is all green...

Is there a way to add getAllowInsecureContinueWhenDisabled to all repositories automatically, including ones use for plugin resolution in settings.gradle? https://github.com/gradle/gradle/pull/36060 completely broke offline use cases. These reproducable build changes are so painful.

Hi, I've been wondering why gradle is using https://repo.maven.apache.org/maven2/ (https://github.com/gradle/gradle/blob/master/subprojects/core-api/src/main/java/org/gradle/api/artifacts/ArtifactRepositoryContainer.java#L54) as default url for maven central while apache declares that it is not the proper url and

<https://repo1.maven.org/maven2>

(https://central.sonatype.org/consume/) should be used instead.

Hi, every time I run './gradlew wrapper' with 9.5.0, the new retry values are reset to their defaults once I set a number of retries, shouldn't it keep the values I set?

Can I reliably capture gradle invocation error

Execution failed for task ':feature:a:compileDebugUnitTestKotlin' (registered by plugin 'com.android.internal.library').
> A failure occurred while executing org.jetbrains.kotlin.compilerRunner.btapi.BuildToolsApiCompilationWork
   > Compilation error. See log for more details

So later in CI step I can print it?

I'm trying to debug an issue as to why a sync on my new teams codebase takes like 30 seconds each time you sync. You can simply just add a

val blah = 0

to the build file (app build file specifically since this is an android project) and if I hit sync, it'll take 30 seconds. I figured it out. Ordering of repositories was wrong so it was going to one really slow maven repo mirror first which never had anything. Cool problem solved... but now I'm starting to go a little stir crazy. what does adding

val blah = 0

require a dependency refresh. i could literally sync, wait 30 seconds, add

val blah2 = 0

sync and its gotta wait 30 seconds again. I thought the point of gradle is that it caches these things so it wouldn't need to check in for each dep again. I feel like I'm misunderstanding something and claude/codex are giving me conflicting answers.

getting failures resolving dependencies in my android project. the artifact repo is a 3rd party (not moven or google) this is the error: ""failed: Connect timed out" does this just mean that it tried connecting for 30 seconds and it failed? or is there some other timeout. trying to let the 3rd party know. https://github.com/gradle/gradle/blob/master/platforms/software/resources-http/src/main/java/org/gradle/internal/resource/transport/http/JavaSystemPropertiesHttpTimeoutSettings.java#L61 It connects like 90% of the time, but like 10% of the time i get the timeout messaging in CI

Hi all! What is Gradle actually using internally to compare two artifact versions to determine which one is newer?

org.gradle.util.internal.VersionNumber

eventually? I figured that has a problem (at least in 9.4.0 which I'm checking against) when comparing numbers with three digits against such with four (e.g. "1.2.3.4" is determined to be "older" than "1.2.3"). I need this for some custom build magic.

On an entirely different note, what do I have to do to let Gradle get it's cache under control? For example,

.gradle/caches/9.4.1/kotlin-dsl

has 2.4G worth of files for only two different (big) monorepo checkouts:

$ du -hs *
2.4G	accessors
199M	scripts

The projects use a central

build-logic

convention module with plain Gradle plugins (no Kotlin DSL there). The only Kotlin DSL in use is in the various build gradle files.

can somone help me wiht my gradlew build fail issue FAILURE: Build failed with an exception. * Where: Build file 'C:\Users\vyasd\cameramod_forge\build.gradle' line: 42 * What went wrong: Could not compile build file 'C:\Users\vyasd\cameramod_forge\build.gradle'.

startup failed:

build file 'C:\Users\vyasd\cameramod_forge\build.gradle': 42: only buildscript {}, pluginManagement {} and other plugins {} script blocks are allowed before plugins {} blocks, no other statements are allowed For more information on the plugins {} block, please refer to https://docs.gradle.org/8.5/userguide/plugins.html#sec:plugins_block in the Gradle documentation. @ line 42, column 1. plugins { ^ 1 error * 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 3s