jsr-305 | Automatically exported from code.google.com/p/jsr-305

When I add Hystrix support to a kotlin spring boot project, some fields of an abstract class are suddenly null. It seems the Hystrix proxy does not handle fields properly:

I have an abstract kotlin class ClientHandler having two fields logger and test directly initialized. I have a kotlin subclass SomeHandler of ClientHandler which I use via autowiring in a class. As expected when using the subclass the two fields are initialized.

But when I add Hystrix support (uncomment @EnableHystrix and @HystrixCommand) the two fields logger and test in the abstract class are suddenly null.

Do you have any ideas why this happens? Spring adds a proxy class to the SomeHandler class, Hystrix does the same. So I assume something goes wrong in the double proxying in combination with Kotlin!? I did the same with a java class and everything went fine.

I'm using Kotlin with https://github.com/vojtechhabarta/typescript-generator to generate TypeScript definitions for my classes that are used in an API.

To preserve nullability information, typescript-generator can use annotations present on fields and methods. It supports arbitrary annotation class names, listed in the build script.

Kotlin, for some reason, annotates nullable fields with @org.jetbrains.annotations.Nullable rather than the JSR-305 annotation, @javax.annotation.Nullable.

While the JSR-305 annotation has RetentionPolicy.RUNTIME, the Jetbrains annotation has RetentionPolicy.CLASS, making it unsuitable for introspection by libraries which use Java Reflection to detect annotations.

Is it possible to have Kotlin generate standards-based annotations instead of the JetBrains proprietary annotations?

If not, I'm interested in simple solutions to handle the issue. Perhaps a Gradle plugin that can generate JSR-305 annotations from the JetBrains ones or similar. I would really prefer to not have to double-annotate everything with a ? and @Nullable.

Building bazel-0.5.0rc9 failed for BadExitStatusException: Process exited with status 50. Terminal output error as follow

How can an OSGi bundle become active without Bundle-Activator in the MANIFEST-MF file? For example, Google guava can run as a bundle and become active in Karaf container but the MANIFEST-MF file doesn't include Bundle-Activator property.

I am generating Java source files for my project using a source generation tool (antlr). However, I am writing most, if not all of my code, in Kotlin.

Kotlin already offers great Java interop, so using the generated sources is not a problem. However, because of how Kotlin brings Java's nullable types into a null-safe system, I lose most of the null-safety that I use Kotlin for. At the very best I have warnings of platform types (make type explicit to avoid subtle bugs); at the worst I have unexpected crashes and subtle bugs.

Kotlin does, however, respect nullability annotations, such as JSR-305, FindBugs, Lombok, Eclipse, and JetBrains's respective forms of @Nullable/@NonNull, bringing those in as the appropriate non-null type or optional.

Because the code is generated and I have access to the source (and understand how it works), I know which functions can/not return null, and want to annotate them as such so they include neatly into my null-safe code. However, I cannot add annotations directly into the code, as it is generated during the build step and would overwrite any manual changes.

Is it possible to / what is the best way to annotate the nullability of generated java sources for the purpose of use in null-safe code?