# Announcing kotlinx-metadata-jvm library for reading/modifying metadata of Kotlin/JVM class files

**URL:** https://discuss.kotlinlang.org/t/announcing-kotlinx-metadata-jvm-library-for-reading-modifying-metadata-of-kotlin-jvm-class-files/7980
**Category:** Libraries
**Created:** [June 1, 2018, 5:27pm UTC](https://discuss.kotlinlang.org/t/announcing-kotlinx-metadata-jvm-library-for-reading-modifying-metadata-of-kotlin-jvm-class-files/7980 "2018-06-01T17:27:31Z")
**Posts on this page:** 1
**Showing post:** 18

<div class="post-metadata">

### Author: ![udalov](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.kotlinlang.org/udalov/32/5679_2.png) [@udalov](https://discuss.kotlinlang.org/u/udalov)
#### Post date: [June 6, 2019, 4:53pm UTC](https://discuss.kotlinlang.org/t/announcing-kotlinx-metadata-jvm-library-for-reading-modifying-metadata-of-kotlin-jvm-class-files/7980/18 "2019-06-06T16:53:32Z")

</div>

@wumo You’re correct that kotlinx-metadata-jvm doesn’t provide any access to annotations stored in the class file. In fact, there’s no trace of those annotations in the metadata itself (`@kotlin.Metadata` annotation), so they will always need to be loaded by external means. For example, matching the ExecutableElement instance with the function metadata by the JVM signature (passed to `JvmFunctionExtensionVisitor.visit`). We might consider providing a bunch of small libraries on top of kotlinx-metadata-jvm to provide this matching for popular use cases (annotation processing, reflection, class file processing). Could you please [report an issue](https://kotl.in/issue)?

---

_[View the full topic](https://discuss.kotlinlang.org/t/announcing-kotlinx-metadata-jvm-library-for-reading-modifying-metadata-of-kotlin-jvm-class-files/7980)._