closure 1.4.3 → 1.5.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (70) hide show
  1. checksums.yaml +7 -0
  2. data/README.md +12 -12
  3. data/closure-compiler/README.md +503 -0
  4. data/closure-compiler/compiler.jar +0 -0
  5. data/closure-templates/SoyToJsSrcCompiler.jar +0 -0
  6. data/closure-templates/soyutils.js +1593 -469
  7. data/closure-templates/soyutils_usegoog.js +1105 -223
  8. data/docs/SCRIPT.md +5 -5
  9. data/docs/closure/Closure/BeanShell.html +63 -54
  10. data/docs/closure/Closure/Compiler/Compilation.html +124 -107
  11. data/docs/closure/Closure/Compiler/Error.html +28 -21
  12. data/docs/closure/Closure/Compiler.html +81 -76
  13. data/docs/closure/Closure/FileResponse.html +113 -98
  14. data/docs/closure/Closure/Goog.html +264 -253
  15. data/docs/closure/Closure/Middleware.html +66 -55
  16. data/docs/closure/Closure/Script/NotFound.html +28 -21
  17. data/docs/closure/Closure/Script/RenderStackOverflow.html +28 -21
  18. data/docs/closure/Closure/Script.html +212 -203
  19. data/docs/closure/Closure/Server.html +100 -90
  20. data/docs/closure/Closure/ShowExceptions.html +63 -52
  21. data/docs/closure/Closure/Sources.html +254 -246
  22. data/docs/closure/Closure/Templates/Error.html +28 -21
  23. data/docs/closure/Closure/Templates.html +88 -80
  24. data/docs/closure/Closure.html +181 -163
  25. data/docs/closure/_index.html +42 -38
  26. data/docs/closure/class_list.html +19 -8
  27. data/docs/closure/css/full_list.css +4 -2
  28. data/docs/closure/css/style.css +68 -51
  29. data/docs/closure/file.LICENSE.html +24 -217
  30. data/docs/closure/file.README.html +54 -47
  31. data/docs/closure/file_list.html +20 -9
  32. data/docs/closure/frames.html +18 -5
  33. data/docs/closure/index.html +54 -47
  34. data/docs/closure/js/app.js +60 -46
  35. data/docs/closure/js/full_list.js +24 -10
  36. data/docs/closure/js/jquery.js +4 -16
  37. data/docs/closure/method_list.html +74 -175
  38. data/docs/closure/top-level-namespace.html +29 -20
  39. data/lib/closure/compiler.rb +32 -42
  40. data/lib/closure/goog.rb +12 -12
  41. data/lib/closure/server.rb +6 -6
  42. data/lib/closure/show_exceptions.rb +15 -12
  43. data/lib/closure/version.rb +1 -1
  44. data/scripts/git.erb +183 -0
  45. data/scripts/hello/compiler.js.erb +2 -2
  46. data/scripts/hello/hello.js +1 -1
  47. data/scripts/hello/index.erb +6 -0
  48. data/scripts/hello/legume.js +12 -7
  49. data/scripts/index.erb +15 -13
  50. data/scripts/modules/compiler.js.erb +3 -3
  51. data/scripts/modules/compiler_build.js +3 -3
  52. data/scripts/modules/compiler_build.map +13 -12159
  53. data/scripts/modules/compiler_build_api.js +1 -1
  54. data/scripts/modules/compiler_build_app.js +74 -71
  55. data/scripts/modules/compiler_build_settings.js +2 -2
  56. data/scripts/modules/index.erb +5 -3
  57. data/scripts/modules/settings.js +1 -1
  58. data/scripts/svn.erb +11 -11
  59. data/scripts/welcome.erb +7 -6
  60. metadata +65 -81
  61. data/closure-compiler/README +0 -292
  62. data/scripts/hello/compiler_build.js +0 -5
  63. data/scripts/hello/compiler_build.map +0 -748
  64. data/scripts/hello/compiler_debug.js +0 -119
  65. data/scripts/modules/compiler_debug.js +0 -6
  66. data/scripts/modules/compiler_debug_api.js +0 -11
  67. data/scripts/modules/compiler_debug_app.js +0 -2414
  68. data/scripts/modules/compiler_debug_settings.js +0 -39
  69. data/scripts/rails/index.erb +0 -46
  70. data/scripts/rails/rails_ujs.js +0 -96
checksums.yaml ADDED
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA1:
3
+ metadata.gz: db899510196640b0bd5ec4709981043e7cc8c855
4
+ data.tar.gz: 33efb688d9821ba4486517e92e2ad6bfce3bc3ba
5
+ SHA512:
6
+ metadata.gz: 84007577c52f792870d0faabfc6b2eed0566da0f5c627a388d704c8d309081990d4e0c81feeacba26efcef05de89fdeab5921e819982a7c3135152d46cd54828
7
+ data.tar.gz: 74c6ab8c2392f2be6f58b91ead1e52ae5990d6adf82111ac5b5fcb61f12900deedaaf4169984cdb042edfa1fee65d0549624181174d8e4c80a63db75d00adf15
data/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  A development environment for Google Closure Tools.
4
4
 
5
- Licensed under the Apache License, Version 2.0 (the "License");
5
+ Licensed under the Apache License, Version 2.0 (the "License");
6
6
  <http://www.apache.org/licenses/LICENSE-2.0>
7
7
 
8
8
  # Installing
@@ -19,7 +19,7 @@ under Windows. Mac OSX and most Linux will have a compatible Ruby by default.
19
19
  ### Step 1: Download to a new folder
20
20
 
21
21
  cd ~/empty-dir
22
- curl -LO https://github.com/downloads/dturnbull/closure-script/closure-1.4.2.jar
22
+ curl -LO https://github.com/downloads/AE9RB/closure-script/closure-1.4.2.jar
23
23
 
24
24
  ### Step 2: Start server from the new folder
25
25
 
@@ -27,7 +27,7 @@ under Windows. Mac OSX and most Linux will have a compatible Ruby by default.
27
27
 
28
28
  ### Step 3: Open a web browser
29
29
 
30
- http://localhost:8080/
30
+ http://localhost:8080/
31
31
 
32
32
 
33
33
  ## Ruby (.gem)
@@ -40,7 +40,7 @@ under Windows. Mac OSX and most Linux will have a compatible Ruby by default.
40
40
 
41
41
  cd ~/empty-dir
42
42
  closure-script
43
-
43
+
44
44
  ### Step 3: Open a web browser
45
45
 
46
46
  http://localhost:8080/
@@ -49,13 +49,13 @@ under Windows. Mac OSX and most Linux will have a compatible Ruby by default.
49
49
  # The Closure Script Method
50
50
 
51
51
  When you start the server for the first time in an empty folder, the home page
52
- will prompt you to install scaffolding. This includes three example projects to
52
+ will prompt you to install scaffolding. This includes three example projects to
53
53
  demonstrate soy, modules, and unobtrusive markup. Dissecting and working with
54
54
  these examples is the fast track to understanding The Closure Script Method.
55
55
 
56
56
  ## The Server
57
57
 
58
- Closure Script is a high-performance, multi-threaded web application engineered
58
+ Closure Script is a high-performance, multi-threaded web application engineered
59
59
  exclusively for the needs of Google Closure Javascript development.
60
60
 
61
61
  You will be freed from the command line. All error output from the compiler
@@ -70,13 +70,13 @@ Check your Javascript console. Then back to your editor.
70
70
  You'll need to supply the directories where you have source Javascript and static files.
71
71
  Ruby developers will recognize that Closure Script is Rack middleware. This makes it trivial
72
72
  to include the Closure Script build tool in a Rails application. If you're not developing a
73
- Ruby application, your ```config.ru``` will probably never be more complex than the following:
73
+ Ruby application, your `config.ru` will probably never be more complex than the following:
74
74
 
75
75
  require 'closure'
76
76
  Closure.add_source '.', '/'
77
77
  use Closure::Middleware, 'index'
78
78
  run Rack::File.new '.'
79
-
79
+
80
80
  The add_source command may be duplicated for each source Javascript folder you want to
81
81
  serve. The first argument is the local filesystem path, the second is the mount point
82
82
  for the http server. Make sure not to accidentally serve more than one copy of
@@ -96,8 +96,8 @@ also choose to use your main application instead of Closure Script for your demo
96
96
 
97
97
  Files ending with .erb are Closure Scripts and will have their embedded Ruby evaluated
98
98
  as they are served. Scripts may also render other Scripts and pass variables if you
99
- need that complexity. Scripts default to a MIME type of text/html so ```demo.erb``` is
100
- the same as ```demo.html.erb```.
99
+ need that complexity. Scripts default to a MIME type of text/html so `demo.erb` is
100
+ the same as `demo.html.erb`.
101
101
 
102
102
  <html>
103
103
  <head>
@@ -133,14 +133,14 @@ that use the query string.
133
133
  ### Testing
134
134
 
135
135
  Closure Script helps with testing because it can see your data in ways that
136
- browsers are not allowed to. The ```alltests.js``` file in Closure Library is
136
+ browsers are not allowed to. The `alltests.js` file in Closure Library is
137
137
  generated by a program that scans the filesystem. Here's a replacement in
138
138
  Closure Script so that a manual build step never has to be executed again:
139
139
 
140
140
  <% all_test_files = Dir.glob expand_path '**/*_test.html'
141
141
  json_strings = all_test_files.map { |x| relative_src(x).dump }
142
142
  -%>var _allTests = [<%= json_strings.join(',') %>];
143
-
143
+
144
144
  Since all of Ruby is at your disposal, you could even pull fixture data from SQL
145
145
  or a web service. Perhaps a fixture refresh happens when the developer pushes a
146
146
  form button. The svn.erb tool is a complex example that uses threads and a
@@ -0,0 +1,503 @@
1
+ # [Google Closure Compiler](https://developers.google.com/closure/compiler/)
2
+
3
+ [![Build Status](https://travis-ci.org/google/closure-compiler.svg?branch=master)](https://travis-ci.org/google/closure-compiler)
4
+
5
+ The [Closure Compiler](https://developers.google.com/closure/compiler/) is a tool for making JavaScript download and run faster. It is a true compiler for JavaScript. Instead of compiling from a source language to machine code, it compiles from JavaScript to better JavaScript. It parses your JavaScript, analyzes it, removes dead code and rewrites and minimizes what's left. It also checks syntax, variable references, and types, and warns about common JavaScript pitfalls.
6
+
7
+ ## Getting Started
8
+ * [Download the latest version](http://dl.google.com/closure-compiler/compiler-latest.zip) ([Release details here](https://github.com/google/closure-compiler/wiki/Releases))
9
+ * [Download a specific version](https://github.com/google/closure-compiler/wiki/Binary-Downloads). Also available via:
10
+ - [Maven](https://github.com/google/closure-compiler/wiki/Maven)
11
+ - [NPM](https://www.npmjs.com/package/google-closure-compiler)
12
+ * See the [Google Developers Site](https://developers.google.com/closure/compiler/docs/gettingstarted_app) for documentation including instructions for running the compiler from the command line.
13
+
14
+ ## Options for Getting Help
15
+ 1. Post in the [Closure Compiler Discuss Group](https://groups.google.com/forum/#!forum/closure-compiler-discuss)
16
+ 2. Ask a question on [Stack Overflow](http://stackoverflow.com/questions/tagged/google-closure-compiler)
17
+ 3. Consult the [FAQ](https://github.com/google/closure-compiler/wiki/FAQ)
18
+
19
+ ## Building it Yourself
20
+
21
+ Note: The Closure Compiler requires [Java 7 or higher](http://www.java.com/).
22
+
23
+ ### Using [Maven](http://maven.apache.org/)
24
+
25
+ 1. Download [Maven](http://maven.apache.org/download.cgi).
26
+
27
+ 2. Run `mvn -DskipTests` (omit the `-DskipTests` if you want to run all the
28
+ unit tests too).
29
+
30
+ This will produce a jar file called `target/closure-compiler-1.0-SNAPSHOT.jar`.
31
+
32
+ ### Using [Eclipse](http://www.eclipse.org/)
33
+
34
+ 1. Download and open the [Eclipse IDE](http://www.eclipse.org/).
35
+ 2. Navigate to ```File > New > Project ...``` and create a Java Project. Give
36
+ the project a name.
37
+ 3. Select ```Create project from existing source``` and choose the root of the
38
+ checked-out source tree as the existing directory.
39
+ 3. Navigate to the ```build.xml``` file. You will see all the build rules in
40
+ the Outline pane. Run the ```jar``` rule to build the compiler in
41
+ ```build/compiler.jar```.
42
+
43
+ ## Running
44
+
45
+ On the command line, at the root of this project, type
46
+
47
+ ```
48
+ java -jar build/compiler.jar
49
+ ```
50
+
51
+ This starts the compiler in interactive mode. Type
52
+
53
+ ```javascript
54
+ var x = 17 + 25;
55
+ ```
56
+
57
+ then hit "Enter", then hit "Ctrl-Z" (on Windows) or "Ctrl-D" (on Mac or Linux)
58
+ and "Enter" again. The Compiler will respond:
59
+
60
+ ```javascript
61
+ var x=42;
62
+ ```
63
+
64
+ The Closure Compiler has many options for reading input from a file, writing
65
+ output to a file, checking your code, and running optimizations. To learn more,
66
+ type
67
+
68
+ ```
69
+ java -jar compiler.jar --help
70
+ ```
71
+
72
+ More detailed information about running the Closure Compiler is available in the
73
+ [documentation](http://code.google.com/closure/compiler/docs/gettingstarted_app.html).
74
+
75
+ ## Compiling Multiple Scripts
76
+
77
+ If you have multiple scripts, you should compile them all together with one
78
+ compile command.
79
+
80
+ ```bash
81
+ java -jar compiler.jar --js_output_file=out.js in1.js in2.js in3.js ...
82
+ ```
83
+
84
+ You can also use minimatch-style globs.
85
+
86
+ ```bash
87
+ # Recursively include all js files in subdirs
88
+ java -jar compiler.jar --js_output_file=out.js 'src/**.js'
89
+
90
+ # Recursively include all js files in subdirs, excluding test files.
91
+ # Use single-quotes, so that bash doesn't try to expand the '!'
92
+ java -jar compiler.jar --js_output_file=out.js 'src/**.js' '!**_test.js'
93
+ ```
94
+
95
+ The Closure Compiler will concatenate the files in the order they're passed at
96
+ the command line.
97
+
98
+ If you're using globs or many files, you may start to run into
99
+ problems with managing dependencies between scripts. In this case, you should
100
+ use the [Closure Library](https://developers.google.com/closure/library/). It
101
+ contains functions for enforcing dependencies between scripts, and Closure Compiler
102
+ will re-order the inputs automatically.
103
+
104
+ ## How to Contribute
105
+ ### Reporting a bug
106
+ 1. First make sure that it is really a bug and not simply the way that Closure Compiler works (especially true for ADVANCED_OPTIMIZATIONS).
107
+ * Check the [official documentation](https://developers.google.com/closure/compiler/)
108
+ * Consult the [FAQ](https://github.com/google/closure-compiler/wiki/FAQ)
109
+ * Search on [Stack Overflow](http://stackoverflow.com/questions/tagged/google-closure-compiler) and in the [Closure Compiler Discuss Group](https://groups.google.com/forum/#!forum/closure-compiler-discuss)
110
+ 2. If you still think you have found a bug, make sure someone hasn't already reported it. See the list of [known issues](https://github.com/google/closure-compiler/issues).
111
+ 3. If it hasn't been reported yet, post a new issue. Make sure to add enough detail so that the bug can be recreated. The smaller the reproduction code, the better.
112
+
113
+ ### Suggesting a Feature
114
+ 1. Consult the [FAQ](https://github.com/google/closure-compiler/wiki/FAQ) to make sure that the behaviour you would like isn't specifically excluded (such as string inlining).
115
+ 2. Make sure someone hasn't requested the same thing. See the list of [known issues](https://github.com/google/closure-compiler/issues).
116
+ 3. Read up on [what type of feature requests are accepted](https://github.com/google/closure-compiler/wiki/FAQ#how-do-i-submit-a-feature-request-for-a-new-type-of-optimization).
117
+ 4. Submit your request as an issue.
118
+
119
+ ### Submitting patches
120
+ 1. All contributors must sign a contributor license agreement (CLA).
121
+ A CLA basically says that you own the rights to any code you contribute,
122
+ and that you give us permission to use that code in Closure Compiler.
123
+ You maintain the copyright on that code.
124
+ If you own all the rights to your code, you can fill out an
125
+ [individual CLA](http://code.google.com/legal/individual-cla-v1.0.html).
126
+ If your employer has any rights to your code, then they also need to fill out
127
+ a [corporate CLA](http://code.google.com/legal/corporate-cla-v1.0.html).
128
+ If you don't know if your employer has any rights to your code, you should
129
+ ask before signing anything.
130
+ By default, anyone with an @google.com email address already has a CLA
131
+ signed for them.
132
+ 2. To make sure your changes are of the type that will be accepted, ask about your patch on the [Closure Compiler Discuss Group](https://groups.google.com/forum/#!forum/closure-compiler-discuss)
133
+ 3. Fork the repository.
134
+ 4. Make your changes.
135
+ 5. Submit a pull request for your changes. A project developer will review your work and then merge your request into the project.
136
+
137
+ ## Closure Compiler License
138
+
139
+ Copyright 2009 The Closure Compiler Authors.
140
+
141
+ Licensed under the Apache License, Version 2.0 (the "License");
142
+ you may not use this file except in compliance with the License.
143
+ You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.
144
+
145
+ Unless required by applicable law or agreed to in writing, software
146
+ distributed under the License is distributed on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
148
+ See the License for the specific language governing permissions and
149
+ limitations under the License.
150
+
151
+ ## Dependency Licenses
152
+
153
+ ### Rhino
154
+
155
+ <table>
156
+ <tr>
157
+ <td>Code Path</td>
158
+ <td>
159
+ <code>src/com/google/javascript/rhino</code>, <code>test/com/google/javascript/rhino</code>
160
+ </td>
161
+ </tr>
162
+
163
+ <tr>
164
+ <td>URL</td>
165
+ <td>http://www.mozilla.org/rhino</td>
166
+ </tr>
167
+
168
+ <tr>
169
+ <td>Version</td>
170
+ <td>1.5R3, with heavy modifications</td>
171
+ </tr>
172
+
173
+ <tr>
174
+ <td>License</td>
175
+ <td>Netscape Public License and MPL / GPL dual license</td>
176
+ </tr>
177
+
178
+ <tr>
179
+ <td>Description</td>
180
+ <td>A partial copy of Mozilla Rhino. Mozilla Rhino is an
181
+ implementation of JavaScript for the JVM. The JavaScript
182
+ parse tree data structures were extracted and modified
183
+ significantly for use by Google's JavaScript compiler.</td>
184
+ </tr>
185
+
186
+ <tr>
187
+ <td>Local Modifications</td>
188
+ <td>The packages have been renamespaced. All code not
189
+ relevant to the parse tree has been removed. A JsDoc parser and static typing
190
+ system have been added.</td>
191
+ </tr>
192
+ </table>
193
+
194
+ ### Args4j
195
+
196
+ <table>
197
+ <tr>
198
+ <td>Code Path</td>
199
+ <td><code>lib/args4j.jar</code></td>
200
+ </tr>
201
+
202
+ <tr>
203
+ <td>URL</td>
204
+ <td>https://args4j.dev.java.net/</td>
205
+ </tr>
206
+
207
+ <tr>
208
+ <td>Version</td>
209
+ <td>2.0.26</td>
210
+ </tr>
211
+
212
+ <tr>
213
+ <td>License</td>
214
+ <td>MIT</td>
215
+ </tr>
216
+
217
+ <tr>
218
+ <td>Description</td>
219
+ <td>args4j is a small Java class library that makes it easy to parse command line
220
+ options/arguments in your CUI application.</td>
221
+ </tr>
222
+
223
+ <tr>
224
+ <td>Local Modifications</td>
225
+ <td>None</td>
226
+ </tr>
227
+ </table>
228
+
229
+ ### Guava Libraries
230
+
231
+ <table>
232
+ <tr>
233
+ <td>Code Path</td>
234
+ <td><code>lib/guava.jar</code></td>
235
+ </tr>
236
+
237
+ <tr>
238
+ <td>URL</td>
239
+ <td>https://github.com/google/guava</td>
240
+ </tr>
241
+
242
+ <tr>
243
+ <td>Version</td>
244
+ <td>20.0</td>
245
+ </tr>
246
+
247
+ <tr>
248
+ <td>License</td>
249
+ <td>Apache License 2.0</td>
250
+ </tr>
251
+
252
+ <tr>
253
+ <td>Description</td>
254
+ <td>Google's core Java libraries.</td>
255
+ </tr>
256
+
257
+ <tr>
258
+ <td>Local Modifications</td>
259
+ <td>None</td>
260
+ </tr>
261
+ </table>
262
+
263
+ ### JSR 305
264
+
265
+ <table>
266
+ <tr>
267
+ <td>Code Path</td>
268
+ <td><code>lib/jsr305.jar</code></td>
269
+ </tr>
270
+
271
+ <tr>
272
+ <td>URL</td>
273
+ <td>http://code.google.com/p/jsr-305/</td>
274
+ </tr>
275
+
276
+ <tr>
277
+ <td>Version</td>
278
+ <td>svn revision 47</td>
279
+ </tr>
280
+
281
+ <tr>
282
+ <td>License</td>
283
+ <td>BSD License</td>
284
+ </tr>
285
+
286
+ <tr>
287
+ <td>Description</td>
288
+ <td>Annotations for software defect detection.</td>
289
+ </tr>
290
+
291
+ <tr>
292
+ <td>Local Modifications</td>
293
+ <td>None</td>
294
+ </tr>
295
+ </table>
296
+
297
+ ### JUnit
298
+
299
+ <table>
300
+ <tr>
301
+ <td>Code Path</td>
302
+ <td><code>lib/junit.jar</code></td>
303
+ </tr>
304
+
305
+ <tr>
306
+ <td>URL</td>
307
+ <td>http://sourceforge.net/projects/junit/</td>
308
+ </tr>
309
+
310
+ <tr>
311
+ <td>Version</td>
312
+ <td>4.11</td>
313
+ </tr>
314
+
315
+ <tr>
316
+ <td>License</td>
317
+ <td>Common Public License 1.0</td>
318
+ </tr>
319
+
320
+ <tr>
321
+ <td>Description</td>
322
+ <td>A framework for writing and running automated tests in Java.</td>
323
+ </tr>
324
+
325
+ <tr>
326
+ <td>Local Modifications</td>
327
+ <td>None</td>
328
+ </tr>
329
+ </table>
330
+
331
+ ### Protocol Buffers
332
+
333
+ <table>
334
+ <tr>
335
+ <td>Code Path</td>
336
+ <td><code>lib/protobuf-java.jar</code></td>
337
+ </tr>
338
+
339
+ <tr>
340
+ <td>URL</td>
341
+ <td>https://github.com/google/protobuf</td>
342
+ </tr>
343
+
344
+ <tr>
345
+ <td>Version</td>
346
+ <td>2.5.0</td>
347
+ </tr>
348
+
349
+ <tr>
350
+ <td>License</td>
351
+ <td>New BSD License</td>
352
+ </tr>
353
+
354
+ <tr>
355
+ <td>Description</td>
356
+ <td>Supporting libraries for protocol buffers,
357
+ an encoding of structured data.</td>
358
+ </tr>
359
+
360
+ <tr>
361
+ <td>Local Modifications</td>
362
+ <td>None</td>
363
+ </tr>
364
+ </table>
365
+
366
+ ### Truth
367
+
368
+ <table>
369
+ <tr>
370
+ <td>Code Path</td>
371
+ <td><code>lib/truth.jar</code></td>
372
+ </tr>
373
+
374
+ <tr>
375
+ <td>URL</td>
376
+ <td>https://github.com/google/truth</td>
377
+ </tr>
378
+
379
+ <tr>
380
+ <td>Version</td>
381
+ <td>0.24</td>
382
+ </tr>
383
+
384
+ <tr>
385
+ <td>License</td>
386
+ <td>Apache License 2.0</td>
387
+ </tr>
388
+
389
+ <tr>
390
+ <td>Description</td>
391
+ <td>Assertion/Proposition framework for Java unit tests</td>
392
+ </tr>
393
+
394
+ <tr>
395
+ <td>Local Modifications</td>
396
+ <td>None</td>
397
+ </tr>
398
+ </table>
399
+
400
+ ### Ant
401
+
402
+ <table>
403
+ <tr>
404
+ <td>Code Path</td>
405
+ <td>
406
+ <code>lib/ant.jar</code>, <code>lib/ant-launcher.jar</code>
407
+ </td>
408
+ </tr>
409
+
410
+ <tr>
411
+ <td>URL</td>
412
+ <td>http://ant.apache.org/bindownload.cgi</td>
413
+ </tr>
414
+
415
+ <tr>
416
+ <td>Version</td>
417
+ <td>1.8.1</td>
418
+ </tr>
419
+
420
+ <tr>
421
+ <td>License</td>
422
+ <td>Apache License 2.0</td>
423
+ </tr>
424
+
425
+ <tr>
426
+ <td>Description</td>
427
+ <td>Ant is a Java based build tool. In theory it is kind of like "make"
428
+ without make's wrinkles and with the full portability of pure java code.</td>
429
+ </tr>
430
+
431
+ <tr>
432
+ <td>Local Modifications</td>
433
+ <td>None</td>
434
+ </tr>
435
+ </table>
436
+
437
+ ### GSON
438
+
439
+ <table>
440
+ <tr>
441
+ <td>Code Path</td>
442
+ <td><code>lib/gson.jar</code></td>
443
+ </tr>
444
+
445
+ <tr>
446
+ <td>URL</td>
447
+ <td>https://github.com/google/gson</td>
448
+ </tr>
449
+
450
+ <tr>
451
+ <td>Version</td>
452
+ <td>2.2.4</td>
453
+ </tr>
454
+
455
+ <tr>
456
+ <td>License</td>
457
+ <td>Apache license 2.0</td>
458
+ </tr>
459
+
460
+ <tr>
461
+ <td>Description</td>
462
+ <td>A Java library to convert JSON to Java objects and vice-versa</td>
463
+ </tr>
464
+
465
+ <tr>
466
+ <td>Local Modifications</td>
467
+ <td>None</td>
468
+ </tr>
469
+ </table>
470
+
471
+ ### Node.js Closure Compiler Externs
472
+
473
+ <table>
474
+ <tr>
475
+ <td>Code Path</td>
476
+ <td><code>contrib/nodejs</code></td>
477
+ </tr>
478
+
479
+ <tr>
480
+ <td>URL</td>
481
+ <td>https://github.com/dcodeIO/node.js-closure-compiler-externs</td>
482
+ </tr>
483
+
484
+ <tr>
485
+ <td>Version</td>
486
+ <td>e891b4fbcf5f466cc4307b0fa842a7d8163a073a</td>
487
+ </tr>
488
+
489
+ <tr>
490
+ <td>License</td>
491
+ <td>Apache 2.0 license</td>
492
+ </tr>
493
+
494
+ <tr>
495
+ <td>Description</td>
496
+ <td>Type contracts for NodeJS APIs</td>
497
+ </tr>
498
+
499
+ <tr>
500
+ <td>Local Modifications</td>
501
+ <td>Substantial changes to make them compatible with NpmCommandLineRunner.</td>
502
+ </tr>
503
+ </table>
Binary file