@@ -76,19 +76,29 @@ More detailed information about running the Closure Compiler is available in the
76
76
If you have multiple scripts, you should compile them all together with one
77
77
compile command.
78
78
79
+ ``` bash
80
+ java -jar compiler.jar --js_output_file=out.js in1.js in2.js in3.js ...
79
81
```
80
- java -jar compiler.jar --js=in1.js --js=in2.js ... --js_output_file=out.js
82
+
83
+ You can also use minimatch-style globs.
84
+
85
+ ``` bash
86
+ # Recursively include all js files in subdirs
87
+ java -jar compiler.jar --js_output_file=out.js ' src/**.js'
88
+
89
+ # Recursively include all js files in subdirs, exclusing test files.
90
+ # Use single-quotes, so that bash doesn't try to expand the '!'
91
+ java -jar compiler.jar --js_output_file=out.js ' src/**.js' ' !**_test.js'
81
92
```
82
93
83
94
The Closure Compiler will concatenate the files in the order they're passed at
84
95
the command line.
85
96
86
- If you need to compile many, many scripts together , you may start to run into
97
+ If you're using globs or many files , you may start to run into
87
98
problems with managing dependencies between scripts. In this case, you should
88
99
use the [ Closure Library] ( https://developers.google.com/closure/library/ ) . It
89
- contains functions for enforcing dependencies between scripts, and a tool
90
- called ```` calcdeps.py ```` that knows how to give scripts to the Closure Compiler
91
- in the right order.
100
+ contains functions for enforcing dependencies between scripts, and Closure Compiler
101
+ will re-order the inputs automatically.
92
102
93
103
## How to Contribute
94
104
### Reporting a bug
0 commit comments