From f7eac7a2ac71296333075a6b0b0022e476f2de10 Mon Sep 17 00:00:00 2001 From: Colin Cross Date: Thu, 8 Feb 2018 12:48:39 -0800 Subject: [PATCH] Fix comment on how java rules handle unknown output files Test: none Change-Id: I985e7961c87dd145d6eb2bd94cb8bdc43becc360 --- java/builder.go | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/java/builder.go b/java/builder.go index 9e3806550..46de4f73c 100644 --- a/java/builder.go +++ b/java/builder.go @@ -35,9 +35,9 @@ var ( // Compiling java is not conducive to proper dependency tracking. The path-matches-class-name // requirement leads to unpredictable generated source file names, and a single .java file // will get compiled into multiple .class files if it contains inner classes. To work around - // this, all java rules write into separate directories and then a post-processing step lists - // the files in the the directory into a list file that later rules depend on (and sometimes - // read from directly using @) + // this, all java rules write into separate directories and then are combined into a .jar file + // (if the rule produces .class files) or a .srcjar file (if the rule produces .java files). + // .srcjar files are unzipped into a temporary directory when compiled with javac. javac = pctx.AndroidGomaStaticRule("javac", blueprint.RuleParams{ Command: `rm -rf "$outDir" "$annoDir" "$srcJarDir" && mkdir -p "$outDir" "$annoDir" "$srcJarDir" && ` +