<@U3ZLHBTLG> I tried the code in the thread and th...

# refreshversions

[dave08]

@louiscad I tried the code in the thread and the refreshVersions task on the main project still updates the versions.properties in mylib instead of the one in the setting.gradle.kts's path in the main project... is there any workaround?

[dave08]

// settings.gradle.kts in the MAIN project, not the one in mylib...

refreshVersions {
    enableBuildSrcLibs()

    versionsPropertiesFile = File("./versions.properties")
}

enableFeaturePreview("TYPESAFE_PROJECT_ACCESSORS")

include(":app")

includeBuild("../mylib")

[Nikky]

try .absoluteFile maybe ?

[Nikky]

that way resolving it from anywhere else will not change the path

[dave08]

That might be an idea! I'll give it a try.

[Nikky]

i think internally it might just assume the highest project up in the filetree is the root or such..
i will dig into the code later and see if i can pinpoint the fault..
(i bet the entire codebase changed from last time i had a look at it)

[dave08]

Thanks for looking into this 👍🏼!

It looks like something changed... I suddenly got this error:

com/android/build/api/extension/AndroidComponentsExtension

* Try:
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Exception is:
java.lang.NoClassDefFoundError: com/android/build/api/extension/AndroidComponentsExtension
	at androidx.navigation.safeargs.gradle.SafeArgsPlugin.apply(SafeArgsPlugin.kt:73)
	at androidx.navigation.safeargs.gradle.SafeArgsPlugin.apply(SafeArgsPlugin.kt:42)
...

it could be it's now looking at the other versions.properties file and starting to find problems with deps...

[louiscad]

I think it's a safeargs plugins issue where it's not compatible with latest AGP.

[dave08]

7.1.1? I upgraded before this in BOTH projects (but had safeargs in the plugins block commented)... before I switched to absoluteFile , once I switched, this error appeared...

[louiscad]

I'd try with AGP 7.0 if possible

[louiscad]

Or 7.0.3 I think

[dave08]

https://stackoverflow.com/questions/70857476/unable-to-load-class-androidcomponentsextension-after-upgrading-the-android-grad that's what I did... I think my deps versions resolution is going nuts now...

[dave08]

Before I just upgraded to 2.4.1..

[louiscad]

Which refreshVersions version are you on?

[dave08]

latest

[louiscad]

The one released last weekend?

[louiscad]

Are you using Gradle configuration cache?

[dave08]

yes.

not that I know

[louiscad]

I'd try running a Gradle clean in the included build, then in the other build

[dave08]

classpath(AndroidX.navigation.safeArgsGradlePlugin.withVersion("2.5.0-alpha01"))

seems to work, but versions.properties still from project B... even WITH absoluteFile...

[louiscad]

Can you print the asbolute path in the Gradle script, to ensure it's the path you are expecting?

[dave08]

Though I didn't see any plugin.{...} for safeArgs in either... I needed to add the withVersion for it to work.

[dave08]

Wow... I think it's completely ignoring the versions.properties from BOTH... I have Kotlin at 1.5.32 in BOTH and it just upgraded me to 1.6...

[dave08]

Even though the refreshVersions task updates project B

[louiscad]

Can you print the asbolute path in the Gradle script, to ensure it's the path you are expecting?

[dave08]

Oh... /home/david/.gradle/daemon/7.3.3/./versions.properties

[louiscad]

Looks like it's not the right place 🧐

[louiscad]

Now, I think it's because of the dot and the leading slash, that's not the right way to refer to the current directory

[louiscad]

And you're using File(…) from <http://java.io|java.io> instead of file(…) from Gradle which will be a relative link (granted you don't put ./ at the beginning of your path.

[louiscad]

If you want to refer to a parent directory, you can use rootDir.parent!!, then .resolve(…)

[dave08]

I tried versionsPropertiesFile = rootProject.projectDir.absoluteFile.resolve("versions.properties") which seems to print the right path... but I get:
* What went wrong:
Execution failed for task ':refreshVersions'.

Can't get latest most stable version in an empty list

[louiscad]

Getting better. Are the repositories properly declared in both projects?

[dave08]

It seems like refreshVersions task has a different way of locating things as the actual dep resolution?

[louiscad]

I'm not sure what you mean by "locating things"

[dave08]

Are the repositories properly declared in both projects?

each project has their own deps. It was working with project B's versions.properties before I changed the path...

locating the versions.properties?

[louiscad]

Anyway, trying to answer what I guess you need to know: refreshVersions looks for versions in the configured versions.properties file or what's provided, and if it finds the version when Gradle decides it's time to look at the dependencies of a project, fine, otherwise, it'll block that Gradle callback while it tries to find the latest most stable version. If it can't find the right version, e.g. because no correct repositories has been defined, or because none have the declared artifact, it fails.

[louiscad]

@dave08 Can you copy paste the exact version of refreshVersions you are using here, not just because I want to be 100% sure, but also for future reference?

[dave08]

id("de.fayard.refreshVersions") version "0.40.1"

[dave08]

in both projects

[louiscad]

Thank you 🙂
About the repositories, did you check?

[dave08]

Which repositories?

[louiscad]

In Gradle

[louiscad]

repositories {
    ... // <-- what you have here
}

[louiscad]

And possibly the dependencyResolutionManagement block in settings.gradle[.kts]

[dave08]

Same repositories in both projects

[louiscad]

blob thinking fast

[dave08]

It works when I don't try changing the path...

[dave08]

but with project B's version.properties

[louiscad]

It's getting too complicated for me to follow the possibilities, can you please make a minimized reproducing project and open an issue on GitHub?

[Nikky]

looking at this again (even before you had those unexplainable cache failures)
i think the last state of support on includeBuild that i know of is .. not supported
i tried to implement that myself a while back but.. gradle is weird

[Nikky]

because of how refreshVersions applies itself.. included builds are tricky to support.. or at least have been in the past..

[louiscad]

but.. gradle is weird

Mandatory link: https://twitter.com/Louis_CAD/status/1491500852871315458?s=20&amp;t=Yo36TOyFbVbqzKEkQ_dODA

[Nikky]

questions.. i have questions...

[louiscad]

Well, Gradle has been named as a pain point in KMM by a fair share of people in the surveys conducted by JetBrains, so making Kotlin more build-agnostic gained some interest as a result. I can see Google making it harder with the state of Android tooling that is centered around the Android Gradle Plugin and Android Studio which is quite tightly coupled to it.