Packaging J2clCommandLineRunner as a standalone binary about j2cl HOT 2 CLOSED

java_binary's deploy target is the one used for deployment:
https://docs.bazel.build/versions/2.0.0/tutorial/java.html#package-a-java-target-for-deployment

Also see:
https://docs.bazel.build/versions/master/be/java.html#java_binary_implicit_outputs

w.r.t size:
J2CL deps are not fine tuned for open-source and brings whole maven dependencies into deployment jar. This could be optimized but wasn't a concern for us so far.

from j2cl.

@cgrushko helped me look at the output and we realized that:

• I could build the J2clCommandLineRunner_deploy.jar rule and use that jar, alongside with the wrapper script.
• The runfiles include a copy of the JRE, which we don't (really?) need.
• I edited the J2clCommandLineRunner script to remove the need of the runtime files as well as set the JAVABIN variable to $(which java).

This got me here:

$ ll
total 26424
-r-x--x--x. 1 XXX users    14177 Feb  3 03:48 J2clCommandLineRunner
-r-xr-xr-x. 1 XXX users 27040744 Feb  3 03:48 J2clCommandLineRunner_deploy.jar
$ du . -sh
26M	.
$ ./J2clCommandLineRunner --singlejar
Error: Argument "<source files>" is required
Usage: j2cl <options> <source files>
use -help for a list of possible options
1 error(s), 0 warning(s).
$

Maybe some of my assumptions are wrong here - but maybe this is good enough.

Closing the issue.

from j2cl.