A modern programming language that makes developers happier.

kotlinlang

<@UDAFKA7NY> FYI the name changed from `common` to `metadata` because we expected the meaning of these artifact to change, too, and this is kind of what's happening.

We have plans to update the layout of these artifacts, which will contain the Kotlin metadata for all of the library source sets and some additional data describing the project structure, which should help the consumer side correctly discover the library declarations.

I agree that the name change might have led to some unexpected confusion, but I suppose leaving the `*-common` suffix would eventually bring even more perplexity, as the old-style `*-common` artifacts and the new `*-metadata` ones won't be interchangeable really soon (though the tools will still be able to read both, of course).

The word *metadata* is used here as it's what we call the binaries that are produced from common code and contain serialized Kotlin declarations.
Thread in Slack Conversation