dwtj / dwtj_rules_java Goto Github PK

Here's one way to make no class files be generated by the javac invocation:

dwtj_java_binary(
    name = "useless_binary",
    srcs = ["EmptyFile.java"],
)

where EmptyFile.java is empty. This currently results in a rather unhelpful error saying that an internal temporary directory for class files doesn't exist.

This is admittedly a very rare case to handle. But making this more robust might help prevent problems with some other less silly cases.

This might be related to #3.

Some JARs are "executable" in the sense that they can be run directly with java -jar. This is supported by setting a main class in the JAR's manifest file.

It may be convenient to be able to run such JARs using bazel run. The java_import rule could support this. An executable boolean attribute could be added to the rule to let the user indicate whether a JAR is in fact executable.

I suspect that this can probably be done by just modifying the rule's run shell script template to include a "$@" at the end of the java command invocation.