so @JvmField kinda generates metadata twice, once ...

# announcements

[Bernhard]

so @JvmField kinda generates metadata twice, once for kotlin and once for java?

[Pavlo Liapota]

What do you mean by compatible with java?
You can assess Kotlin property from Java.
@JvmField instructs compiler to define just a field instead of getter, setter and backing field.

[Bernhard]

I see, thank you

[Bernhard]

my issue is with protected properties

[Bernhard]

apparently you can't access the field directly without @JvmField annotation, only the getters/setters

[Bernhard]

I suppose this is because you want get get() and set() to work

[Pavlo Liapota]

Do you want to get java field, i.e. java.lang.reflect.Field from java reflection or kotlin reflection?
If latter, then this https://kotlinlang.org/docs/reference/reflection.html#interoperability-with-java-reflection may help.

[Bernhard]

no, just plainly accessing the field without getter

[Bernhard]

but thanks for the reflection link

[Bernhard]

will do a company internal presentation highlighting java interop so I'm only trying to figure out the reason when to use these annotations

[Pavlo Liapota]

no, just plainly accessing the field without getter

Ah, I see, then yes, you need @JvmField to do so.

[Pavlo Liapota]

will do a company internal presentation highlighting java interop

Nice! I guess you saw this presentation

https://www.youtube.com/watch?v=zlggmRMadsU▾

?

[Bernhard]

thank you!