The following modules, configuration fragments, and providers will help youĮxtend Bazel’s capabilities when building your Java Not need it when getting started with Bazel. Note: Creating new rules is for advanced build and test scenarios. Tests should be in a matching directory under src/test and depend on thisĬreating new rules for advanced Java builds The sources should be a non-recursive glob of "//package" instead of "//package:package". This makes the label of the library shorter, that is use The name of the library should be the name of the directory containing theīUILD file. Java_library ( name = "directory-name", srcs = glob (), deps =, ) Use one BUILD file per directory containing Java sources, because thisĮvery BUILD file should contain one java_library rule that looks like Prefer Maven’s standard directory layout (sources under src/main/java, testsįollow these guidelines when creating your BUILD files: In addition to general Bazel best practices, below areīest practices specific to Java projects. To compile using locally installed JDK, that is use the compilation toolchainsįor local JDK, use additional flag mind that this may not work on JDK of arbitrary vendors.Ĭonfiguring Java toolchains.
The compilation toolchains using locally installed JDK are configured, Compiling using locally installed JDKīazel by default compiles using remote JDK, because it is overriding JDK’s That JDK and JVMĪre controlled using -tool_java_language_version and Used in the build process, but are not in the build results.
There is a second pair of JDK and JVM used to build and execute tools, which are Configuring compilation and execution of build tools in Java Tested on the JVM downloaded from a remote repository. To create a hermetic compile, you can use command line flag To configure the JVM used for execution and testing use -java_runtime_versionįlag. Libraries, which means the resulting binaries depend on what is installed on the The resulting binaries are compatible with locally installed JVM in system
IMPROVE.DK COMPILING JAVA CODE
Tests the code with the JVM installed on the local machine. Configuring the JVM used to execute and test the codeīazel uses one JDK for compilation and another JVM to execute and test the code.īy default Bazel compiles the code using a JDK it downloads and it executes and Should set this flag so that Bazel and its users can reference the source code’s Sources in the repository add build -java_language_version= is for example 11. Repository are written in a single Java version. Without an additional configuration, Bazel assumes all Java source files in the the version of the Java runtime that is used to execute the code and to test itĬonfiguring the version of the source code in your repository.the version of the source files in the repository.There are two relevant versions of Java that are set with configuration flags: Migration guide to start building your Maven projects with Bazel: If you currently build your Java projects with Maven, follow the steps in the The following resources will help you work with Bazel on Java projects:
Links to a tutorial, build rules, and other information specific to building This page contains resources that help you use Bazel with Java projects.
0 kommentar(er)
