Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(830)

Unified Diff: third_party/WebKit/Source/devtools/scripts/README.md

Issue 2588843002: DevTools: speed up closure dependency checking (Closed)
Patch Set: re-insert comment Created 3 years, 11 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/WebKit/Source/devtools/scripts/README.md
diff --git a/third_party/WebKit/Source/devtools/scripts/README.md b/third_party/WebKit/Source/devtools/scripts/README.md
index 3f4a28329e878ebbc77c821b8034ebc2ecd73ae4..17c3b3add015c027bf79dbf408225547d8eaf9da 100644
--- a/third_party/WebKit/Source/devtools/scripts/README.md
+++ b/third_party/WebKit/Source/devtools/scripts/README.md
@@ -32,4 +32,4 @@ The easiest way to run the node.js scripts is to use `npm run` which displays al
## Closure
-DevTools manually rolls the closure compiler to ./closure. If you manually roll closure compiler, you will need to re-generate the closure_runner (in ./closure) and jsdoc_validator custom jars using the python scripts in their respective directory. Make sure you use JDK 7 to compile these jars, otherwise they won't run on buildbot. If you compile with JDK 7, anyone with Java 7 or Java 8 should be able to run the jar.
+DevTools manually rolls the closure compiler to ./closure. If you manually roll closure compiler, you will need to re-generate the closure_runner (in ./closure) and jsdoc_validator custom jars using the python scripts in their respective directory.

Powered by Google App Engine
This is Rietveld 408576698