This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

I see quite often this long exception from

extractModuleInfo

task. Do you have suggestions how to get rid of it? Thank you

hey ya'll, having some dependency issues with a minecraft mod I am trying to set up

here is a screenshot of the plugin installed

I'm trying to build my kotlin project then I do not get this error at compilation, running with debug and --scan does not change anything

Hey Folks Is there someone facing the debugger connection issue? I'm trying to debug my unit test. but this error always shows.

What’s the policy which versions of Gradle User Guides are shown in the version picker? At the moment it is latest (8.12.1), 6.1, nightly and 8.5. I would expect the latest version, the latest version -1, and the latest version of 7.X and maybe 6.X. But not 6.1 and 8.5

Does Dataflow Actions have access to the whole build log? I have seen there is

failure

but I would be interested in getting the whole log as sometimes the

failure

does not include all the relevant data (for example, the list of tests that are failing).

Hi, currently we run build in two steps

gradle testCompile --continue --parallel

then

gradle test --continue --parallel

it takes 40m summary when running as

gradle testCompile test --continue --parallel

it takes 35m because of better workers utilization. However, in that case it will run all unaffected tests when there were a compilation failure I want to combine benefits of both approaches and skip all test task if any module compilation failed, but not stopping compilation of the modules (as it works with --continue) How can I do that?

Screenshot (50).png

I am facing this error while building a React Native APK. What went wrong: Execution failed for task 'appconfigureCMakeRelWithDebInfo[x86]'.

com.google.gson.stream.MalformedJsonException: Use JsonReader.setLenient(true) to accept malformed JSON at line 1 column 1 path $

how can i resolve this issue (base) PS C:\Users\aksha\AndroidStudioProjects\cottonix> flutter run Launching lib\main.dart on sdk gphone64 x86 64 in debug mode... FAILURE: Build failed with an exception. * Where: Build file 'C:\Users\aksha\AndroidStudioProjects\cottonix\android\app\build.gradle.kts' line: 1 * What went wrong: An exception occurred applying plugin request [id: 'dev.flutter.flutter-gradle-plugin']

Failed to apply plugin 'dev.flutter.flutter-gradle-plugin'.

> Cannot add task 'generateLockfiles' as a task with that name already exists. * 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 7s Running Gradle task 'assembleDebug'... 8.1s Error: Gradle task assembleDebug failed with exit code 1 (base) PS C:\Users\aksha\AndroidStudioProjects\cottonix>

Hey all! I've been struggling with something in my gradle build, I was wondering if someone has a ready made example for that: I want to shadow just a single dependency (protobuf) when releasing my library using maven-publish. I've tried few setups using #C06TFEALHGA, including copying the work done in Kafka here: https://github.com/apache/kafka/blob/9a2043041d38c6555ce0abf6d1438adb34f565b2/build.gradle, but none of them work for one reason or another: either I stumble on some issue with a wrong generated MANIFEST file, or the pom file doesn't contain the other dependencies that should be declared in the pom (they're simply not there), and so on...

I wanted to post in response to this request from Gradle Team on a defect: https://github.com/gradle/gradle/issues/31438#issuecomment-2589897380. I replied with some details about how to reproduce the problem, and a gradle plugin I created that is experiencing the issue reliably after upgrading to gradle 8.10.2. This details are in this post on github: https://github.com/gradle/gradle/issues/31438#issuecomment-2664493253