As of KGP 2.1 using `associateWith` on a custom co...

# build-tools

[jw]

As of KGP 2.1 using associateWith on a custom compilation seems to depend on the jar output of the target compilation whereas in 2.0 it depended only on the classes. Depending on the jar is problematic because this is was a handy mechanism for creating multi-release jars. But with associateWith depending on the jar, this creates a task cycle.

Is there some other way to do what associateWith was doing without depending on the jar?

[jw]

Maybe it's a .jvm plugin thing? The stdlib build doesn't seem to have this problem.

[jw]

Nah even when I do multiplatform I get the same problem. I don't understand how the stdlib does it.

[tapchicoma]

this change stems from the need to properly support friends paths. We are currently redesigning this aspect of the language and a potential way will drop -Xfriend-path argument and simplify logic

[tapchicoma]

anyway regarding multirelease jars - please open an issue. Maybe we will find a workaround

[jw]

Will do with a sample project and report back here. Thanks!

[jw]

I found https://youtrack.jetbrains.com/issue/KT-75550 which covers my use case. Will add my sample project to that instead of a new issue.

[jw]

Although it's "shelved"? First time seeing that. Should I create a new issue then?

[jw]

I created https://youtrack.jetbrains.com/issue/KT-78269 as well

[tapchicoma]

provided a solution in the issue