Premise: I don’t strictly need that, I’m just expe...

# gradle

[Davide Giuseppe Farella]

Premise: I don’t strictly need that, I’m just experimenting the gradle-dsl + buildSrc

I got this in my Dependencies.kt:

class Classpath( scope: ScriptHandlerScope ) {
    val dependencies: DependencyHandlerScope.() -> Unit = {
        scope.run {
            classpath( kotlin("gradle-plugin", Versions.kotlin))
            classpath("org.jetbrains.kotlin:kotlin-serialization:${Versions.kotlin}")
            classpath("com.android.tools.build:gradle:3.3.0")
            classpath("com.squareup.sqldelight:gradle-plugin:${Versions.sqldelight}")
        }
    }
}

And this in my build.gradle.kts:

buildscript {
    repositories( Repositories.all )
    dependencies( Classpath(this ).dependencies )
}

Is there something wrong here? Sync is running successfully, but I got the warning above my kts file:
build configuration failed, using previous dependencies, run 'gradle tasks' for more information which is not true, since that doesn’t give me more info 😄

[gildor]

Did you try to run build from cpmmand line? does it work or not?

[gildor]

just a side note, don’t think that you need class in this case, a function with ScriptHandlerScope argument should be enough

[Davide Giuseppe Farella]

I do, because classpath is an extension function of DependencyHandler, declared inside ScriptHandlerScope

[Davide Giuseppe Farella]

BUILD SUCCESSFUL in 1m 13s

[Davide Giuseppe Farella]

Only a warning Unsupported Kotlin plugin version. I guess because of the deprecated kotlin-dsl plugin on 1.3.20 ( I’m googling for a solution for that 😄 )

[gildor]

Why not just

fun DependencyHandlerScope.dependencies(scope: ScriptHandlerScope) {
        scope.run {
            classpath( kotlin("gradle-plugin", Versions.kotlin))
            classpath("org.jetbrains.kotlin:kotlin-serialization:${Versions.kotlin}")
            classpath("com.android.tools.build:gradle:3.3.0")
            classpath("com.squareup.sqldelight:gradle-plugin:${Versions.sqldelight}")
        }
    }

[gildor]

dependencies( Classpath(this ).dependencies(this))

[Davide Giuseppe Farella]

Yes, that could be better, just trying with the “common pattern” for buildSrc, since I seen nested objects don’t work, for instance, but I guess my warning would persist. I’mma try to invalidate the cache, just in case

[gildor]

nested objects don’t work, for instance

What do you mean?

[Davide Giuseppe Farella]

I’ve tried that, but Kotlin and Android are not resolved

object Versions {
    ...
}

object Libs {
    object Kotlin {
        ...
    }
    object Android {
        ....
    }
}

[gildor]

This works.

[gildor]

Maybe you just have some tooling problem, but it’s valid syntax

[gildor]

and we even use it in our buildSrc

[Davide Giuseppe Farella]

maybe something wrong about that:

plugins {
    `kotlin-dsl`
}

repositories {
    jcenter()
}

[gildor]

@Davide Giuseppe Farella
https://pl.kotl.in/S1mcrNh7V

[gildor]

no, nothing wrong

[gildor]

Do you have some sample project?

[Davide Giuseppe Farella]

Yes, I know that would work normally, just don’t know about buildSrc

[gildor]

buildSrc is just Kotlin code, not even scripting

[Davide Giuseppe Farella]

Imma publish on github, just a new project

[Davide Giuseppe Farella]

here it is https://github.com/4face-studi0/FreshTv-android

[gildor]

And do you have example where nested object doesn’t work?

[Davide Giuseppe Farella]

Imma add it now

[Davide Giuseppe Farella]

Damn, that worked now 😄 so embaracing 😄 Idk what happened 🙈

Also tried some days ago on a multiplaform project

[gildor]

buildSrc is just a Kotlin code, so everything what works for Kotlin code should work there

[gildor]

excluding some bugs (I remember problems with nested subclasses resolution in IDEA a few months ago, but now everything should work and it was tooling only problem)

[Davide Giuseppe Farella]

before I tried with Libs.Android.test = “bla.blablabla”, everything ok but just NOT resolved “bla.bla…” obviously, now I tried with a real deps and got that ( sync successfully )

[Davide Giuseppe Farella]

message has been deleted

[gildor]

I didn’t get what you mean

[gildor]

Does build is successful?

[gildor]

You see, you have failed syncronization

[gildor]

so nothing is syncronized

[Davide Giuseppe Farella]

appcompat is not resolved ( IDE says )

[Davide Giuseppe Farella]

Yes, that warning is what I was talking about 😛

[gildor]

Yes

[gildor]

it means that sync is failed

[gildor]

see logs

[gildor]

Most probably you have some error in your buildSrc or your configs

[Davide Giuseppe Farella]

Just noticed those errors in my sync ( even if successfully )

[TAG] Failed to resolve variable '${project.groupId}'	
[TAG] Failed to resolve variable '${project.version}'	
[TAG] Failed to resolve variable '${version.asm}'	
[TAG] Failed to resolve variable '${version.junit}'	
[TAG] Failed to resolve variable '${version.mockito}'	
[TAG] Failed to resolve variable '${version.asm}'	
[TAG] Failed to resolve variable '${project.groupId}'	
[TAG] Failed to resolve variable '${project.version}'	
[TAG] Failed to resolve variable '${version.junit}'	
[TAG] Failed to resolve variable '${version.mockito}'

[gildor]

no, this is not related

[gildor]

AS is pretty bad in reporting configuration time errors

[gildor]

you said that build is successful, are you sure about this?

[Davide Giuseppe Farella]

Yep, I’ve also wondered that 😕 it’s just a new project, I don’t have any files, out of that gradle ones 😄

[Davide Giuseppe Farella]

message has been deleted

[gildor]

But you change gradle files, so apparently you have changes

[gildor]

I tried to build you project, and there is error in root build.gradle.kts

[Davide Giuseppe Farella]

Also my properties in Dependencies.kt seems unused, even if they’not.

[gildor]

with pretty clear description

[Davide Giuseppe Farella]

yes, I was in a middle of a change 😄

[Davide Giuseppe Farella]

updated right now

[Davide Giuseppe Farella]

that was about that repositories in Dependencies.kt

[gildor]

Yes

[Davide Giuseppe Farella]

message has been deleted

[Davide Giuseppe Farella]

Are you in the same situation?

[gildor]

Did you update your repo?

[Davide Giuseppe Farella]

what you mean? 🙈

[Davide Giuseppe Farella]

Ah sorry, yes

[gildor]

I mean to let me try, does I have problem with sync or not

[Davide Giuseppe Farella]

It’s updated

[Davide Giuseppe Farella]

I was thinking about the project’s repositories 😄

[gildor]

I imported your project and sync is successful (no build configuration failed message) and nested objects just work. So probably some problem with IDE caches or something like that

[gildor]

message has been deleted

[Davide Giuseppe Farella]

As or IntelliJ? Version?

[Davide Giuseppe Farella]

I always got weird problem when go beta -> stable :D\

[gildor]

AS 3.3

[gildor]

sorry, this is version with nested object

[Davide Giuseppe Farella]

Same version… I’mma try to fresh install 😕

[Davide Giuseppe Farella]

Thanks you very much for your time 🍻

[gildor]

I believe reimport of the project will help

[Davide Giuseppe Farella]

Oh ok, that would save me time 🙂

[gildor]

But careful with “Reimport project” function in AS, it creates an empty build.gradle file

[Davide Giuseppe Farella]

I’ve just removed from my project and imported from folder, as fresh project. Seems ok. The only detail: cmd+b on my dependency in build.gradle.kts keep pointing to the compiled file Libs.class so the properties on Dependencies.kt are still marked as unused, it that normal? I didn’t have this behaviour on IntelliJ

[Davide Giuseppe Farella]

Just for info, not that I care, unless it won’t lead to other issues 🙂

[gildor]

Yeah, unfortunately tooling is not perfect, especially with AS which doesn’t have all the latest fixes from IDEA

[Davide Giuseppe Farella]

Gotcha 👍

[gildor]

also, check that you use Kotlin IDE plugin 1.3.20, there are some fixes for kotlin-dsl