The tool provide a way to create a java jar with all it's dependencies, but it will exclude unused deps from the jar to make it thin.
A dep jar will be in the final jar if:
- It's used by the lib (the tools uses jdeps created by bazel to know that).
- It's an explicit dep of the lib.
Add to your WORKSPACE file:
load("@bazel_tools//tools/build_defs/repo:git.bzl", "git_repository")
git_repository(
name = "java_assembly",
remote = "https://github.com/zacharya19/bazel_java_assembly.git",
commit = "30546e90003b272ae2d9252d3854e4ad6d0c3b16"
)
load("@java_assembly//3rdparty:workspace.bzl", "maven_dependencies")
maven_dependencies()
Add to your BUILD file:
load("@java_assembly//:assembly.bzl", "java_assembly_jar")
java_assembly_jar(
name = "jar",
srcs = glob(["src/main/**/*.java"]),
deps = deps,
main_class = "XXX.XXX.XXX" # optional, if you want the tool to write it in the manifest file.
)
Run bazel build :jar_assembly.
The java_assembly_jar rule will create a java_library named jar with all the args, and an assembly jar named jar_assembly, so you can build both.
- Extend the tool to build java WAR files.
- Write tests.
- Add an examples.
- Better exception handling.