Closed ryansgot closed 2 years ago
Do you need to have enableCompatibilityMetadataVariant
enabled in your project? I'm open to adding it here but I want to understand the use-case. Once everybody has hierarchical project support enabled (and it's on by default since 1.6.20) then the compatibility flag shouldn't be necessary anymore.
My use case is that as a library producer, I wanted to enable the compatibility metadata variant. Other libraries I see, such as Ktor (https://github.com/ktorio/ktor/blob/main/gradle.properties#L28), do this. So when integrating this into a library project that had enableCompatibilityMetadataVariant=true
, the above error is encountered.
However, I was able to get past the build issue if I removed enableCompatibilityMetadataVariant=true
from my project's gradle.properties file.
As for whether to merge or close, I'm happy with either. If you choose not to merge, then I suggest you advise about this issue in the README.md file.
Ok, merging and will include this with next release
Here's the situation:
I was testing out 1.0.0-alpha01 to see if it would be viable for a multiplatform library project I was using. It turns out, assembly of the kotlin metadata failed. I'm not sure if this is what you want to do, but the change in this PR fixes the issue for me. The error message is rather long: