I had found that it works for plain javac invocations, and I believe eamonnmcmanus was the one who confirmed for us that it works with NetBeans. But we had seen a report that it doesn't work with IntelliJ, and we haven't tried Eclipse.
And now... I tried to use module-scope @NullMarked in a Gradle project that uses --release 11, and:
error: annotation type not applicable to this kind of declaration
That's happening even though I see a jspecify-0.2.0.jar (with what looks like the right contents) on the --module-path when I pass -d to Gradle.
[edit: Apparently kotlinc doesn't look under META-INF/versions, either. But that's mostly academic: Users won't need to write JSpecify annotations in Kotlin sources (except in rare cases until KT-47417 is implemented), and even if they do, they won't be putting an annotation on a module.]
[edit: I wonder what Turbine does....]
I had found that it works for plain javac invocations, and I believe eamonnmcmanus was the one who confirmed for us that it works with NetBeans. But we had seen a report that it doesn't work with IntelliJ, and we haven't tried Eclipse.
And now... I tried to use module-scope
@NullMarkedin a Gradle project that uses--release 11, and:That's happening even though I see a
jspecify-0.2.0.jar(with what looks like the right contents) on the--module-pathwhen I pass-dto Gradle.[edit: Apparently kotlinc doesn't look under
META-INF/versions, either. But that's mostly academic: Users won't need to write JSpecify annotations in Kotlin sources (except in rare cases until KT-47417 is implemented), and even if they do, they won't be putting an annotation on a module.][edit: I wonder what Turbine does....]