Tim te Beek

Thanks for offering an alternative @BramliAK ; That could work as well, but I worry a bit about the readability of the code when an import would be closer to...

hi @koppor ! I'm looking at the original classes but not seeing the same input there: https://github.com/JabRef/jabref/blob/ebca33e74ee674515e171036d11edc36e8ddc34e/src/main/java/org/jabref/logic/exporter/GroupSerializer.java#L29-L40 Are there additional changed out of view from the diff above that would...

Alternatively, adding threeten-extra to the plugin itself also seems to work as a workaround for now ``` 4.0.0 my.test openrewrite-test 1.0-SNAPSHOT 21 21 UTF-8 joda-time joda-time 2.2 org.openrewrite.maven rewrite-maven-plugin 6.1.3...

There's additional usages that we'd need to replace for a proper fix: 

I've briefly explored doing a method lookup in the declared type, but it's not pretty, and not sure if such an approach will fully work: ```java private JavaType.@Nullable Method methodInvocationType(PsiElement...

Alternatively we can map Kotlin Primitives to JavaType.Primitive, instead of the Java.Class instances they are now; That would mean recipes written for Java that might use these primitives in their...

Any thoughts as to the `kotlin.Int` mapping to `int` here @knutwannheden ? I feel that would help recipe reuse across languages..

Puzzled for a bit if I could get this going by restructuring a bit, but it needs a closer look.

hi @Swachithreddy ; it's not immediately clear to me from your comment what code would look like before a recipe runs, and what it should look like after a recipe...

Thanks for getting this reduced and started @mvitz ! Looks like an oversight in the parser after the addition of records, which would then cause the annotation to not be...