I am getting a weird error on publishing: ```Exec...

# opensavvy

[altavir]

I am getting a weird error on publishing:

Execution failed for task ':maps-kt-core:generateMetadataFileForJvmPublication'.
> java.io.FileNotFoundException: D:\Work\kscience\maps-kt\maps-kt-core\build\distributions\maps-kt-core-0.4.0-dev-8-resources-jvm.zip (The system cannot find the path specified)

Is it possible that it is caused by opensavvy-resouces producer?

[CLOVIS]

It is the producer that registers this artifact, so maybe 🤔 I've never seen this error so I don't really know

[CLOVIS]

If this is reproducible on a publicly available build, please create an issue and I'll look into it!

[altavir]

Here it is: https://gitlab.com/opensavvy/automation/kotlin-js-resources/-/issues/15

[CLOVIS]

What's surprising me is that I do publish libraries that use it without issues, so there must be something somewhere that makes a difference.

[altavir]

Indeed, It could interfere with a lot of things. In this case it seems that the problem is not with publishing itself, but with hashcode cache checks somehere inside publishing.

[CLOVIS]

Do you have Gradle 9+? I haven't tested yet, I'm planning to do so in the coming ~week

[altavir]

I use Gradle 9.2, but I've checked that the same problem appears if I go back to 8.14

[CLOVIS]

Ok, thanks.

[altavir]

It happens on all metadata tasks in all targets.

[altavir]

It is sad, but Gradle finally became unmanageable with its pursuit of configuration cache.

[CLOVIS]

I have just run ./gradlew publishToMavenCentral in your repo, and it was successful. Is there anything else I can do to reproduce?

[altavir]

Did you use dev branch? Main uses old build that does not rely on opensavvy plugin. I checked and dev publishing from the console still fails.

[CLOVIS]

Ah, my mistake. I can reproduce now, I'll take a look tonight.

[altavir]

Thank you very much.