From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

`./gradlew clean assemble`  works as well. But when running my main function , I get the following error
<https://pastebin.com/Mz6qvuN2>
``` ./gradlew clean assemble 

BUILD SUCCESSFUL in 956ms
4 actionable tasks: 4 executed```

Here's a MVCE

1. Create a new `Kotlin JVM Application` in IntelliJ with a Project JDK of 1.8 and Target JVM version of  `1.8`
2. Add the maven snapshot repository and the dependency to your build.gradle
```repositories {
    maven {
        url "<https://s01.oss.sonatype.org/content/repositories/snapshots/>"
    }
}
dependencies {
    implementation "io.appwrite:sdk-for-kotlin:0.0.0-SNAPSHOT"
}```
3. Create a main function with the following code
```import io.appwrite.Client

suspend fun main () {
   val client = Client()
}```
 4. Run main

I don't get it, that task should be disabled, right? how is it still running? is it because it's enabled `buildSrc` ?

I changed my spotless configuration, and now I'm getting all kinds of garbage. I ran `clean` and tried deleting `~/.gradle` but I still get it

<https://github.com/gradle/gradle/issues/12660>
yes, this makes sense ))

Is the login for `<https://discuss.gradle.org>` broken? It takes me to this login page and then always redirects to the `Unauthorized` page.

Talked too soon. It looks like it’s still not working on Android Studio on the root build script:

These are the plugins in `libs.versions.toml`:

so given:

```[versions]
android.minSdk = "21"
minSdk = "21"```
The following fails to compile:

```Script compilation error:

  Line 95:         setMinSdkVersion(libs.versions.android.minSdk.get())
                                                          ^ Unresolved reference: minSdk```

Hey Jendrik, thanks for doing those videos! I have a question for the first video about the settings file. You suggest putting `includeBuild()` under `dependencyResolutionManagement`. Though there is only `Settings.includeBuild()`, so it will fall through to call that. That felt strange to me. What are your reasons for putting the `includeBuild()` methods there?

but the fact that
```configurations.getByName("implementation").allDependencies.forEach { ... }```
filter accepts both `api` and `implementation` *and* the picture below makes it feel that *api extends implementation* like public inheritance in C++ :smile:
i don't know how is it actually expressed internally (in "implementation details"), since these two configurations are just collections of *jars*, but `api&lt;-implementation` could be a way of thinking it easy.

This has (according to my findings) nothing to do with vfs.

Typically happens if you deploy to an android 12 device. Solution:

<@U02DVV0K7MF> when I try to do it:
```configurations.zip.files.each { artifact -&gt;
  println artifact
}```
I receive this:

&gt; Normally `maxHeapSize` should not be an input for test tasks.
Could you guide me on how to make the above statement true?

In our setup, we have such a snippet that sets `maxHeapSize`.
```tasks.withType(Test) {
  maxHeapSize = rootProject.findProperty("testMaxHeapSize") ?: '1024m'
}```
If I run `gradle test` and then `gradle clean test -PtestMaxHeapSize=2048m` it reruns the tests instead of taking the entry from cache.

Here's a screenshot from build scan comparison:

Unfortunately, I'm back at this problem again. I can see a situation where there are two CI builds, let's say A and B. B starts only after A has finished. They are both executed on the exact same checkout. The difference is the machines they run on and, thus, the memory settings, etc. Now when I compare the build scans from these two builds I can see that B didn't take test results from the cache. The only difference that GE indicates is this: `Input 'jvmArgumentProviders.$0' is in both builds but the values are different.`. I'm not exactly sure what this refers to and I don't seem to be able to reproduce it locally by providing different values through the jvmArgumentsProvider I add either.

Do you know what might be going on here by any chance?

~Anyone an idea why I got this error message in IntelliJ UItimate with kotlin-dsl plugin applied?~
Fixed: After remove and re-add java SDK it works again.