Similar to java_binary and kt_jvm_test (see #815 fixed in github.com//pull/837), kt_jvm_binary should also support env variables.
As mentioned by the docs,
**Note:** This rule does not have all of the features found in [`java_binary`](https://docs.bazel.build/versions/master/be/java.html#java_binary).
It is appropriate for building workspace utilities. `java_binary` should be preferred for release artefacts.
to be appropriate for building workspace utilities, it makes sense to support env variables (for example, setting runfiles locations).
Current workaround is to create a kt_jvm_library then call it from a java_binary.