Lóránt Pintér

One downside I see with this is that after the change IntelliJ will offer up both `@Nullable`s for auto-import.

I don't think introducing the double `@Nullable` annotation and the confusion it brings is worth it for just this use case. I can see a couple ways forward: - abandon...

@bamboo Do you mean to add something like a `@NullableType` that only applies to `ElementType.TYPE_USE` and add it to IntelliJ as one more nullable annotation? I like it! I think...

The only problematic thing in `misc.xml` seems to be `ProjectRootManager@project-jdk-name` which I believe points to a machine-local JDK name... 🤔

Seems like we have a plan. How do we get there?

> We could use this for stuff we have on our internal APIs, though I don't understand what the effect on the public API is and if there is some...

> JSR-305 is basically dead, and large libraries like Guava are actively investigating ways to move to other annotations: [google/guava#2960](https://github.com/google/guava/issues/2960). The current efforts are mostly focused on [jspecify](https://github.com/jspecify/jspecify), which is...

This looks fixed in 1.1-M04, can we get rid of the `JarPatcher` now?

cc @eskatos

From @eskatos: > The native platform version isn’t the sole issue though. > The JarPatcher is also used to unify the jansi version and work around other packaging issues of...