From 41627ade988580364f185e087a6ffe15765cf617 Mon Sep 17 00:00:00 2001 From: László Csomor Date: Wed, 7 Jun 2017 04:06:44 -0400 Subject: Bazel client: explain the name of A-server.jar Also add a helper method to GlobalVariables to retrieve this path, thus concentrating the assumptions about the layout of extracted_binaries in one place. Change-Id: If172b6f5bf4451845ad89d3d488ef2a2c2e5d286 PiperOrigin-RevId: 158241854 --- src/package-bazel.sh | 2 ++ 1 file changed, 2 insertions(+) (limited to 'src/package-bazel.sh') diff --git a/src/package-bazel.sh b/src/package-bazel.sh index 19cda686cd..7851751ada 100755 --- a/src/package-bazel.sh +++ b/src/package-bazel.sh @@ -34,6 +34,8 @@ mkdir -p "${PACKAGE_DIR}" trap "rm -fr ${PACKAGE_DIR}" EXIT cp $* ${PACKAGE_DIR} +# The server jar needs to be the first binary we extract. This is how the Bazel +# client knows what .jar to pass to the JVM. cp ${DEPLOY_JAR} ${PACKAGE_DIR}/A-server.jar cp ${INSTALL_BASE_KEY} ${PACKAGE_DIR}/install_base_key # The timestamp of embedded tools should already be zeroed out in the input zip -- cgit v1.2.3