You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: utils/build/compiler/README.md
+66-77Lines changed: 66 additions & 77 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,10 @@
5
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
6
7
7
## Getting Started
8
-
*[Download the latest version](http://dl.google.com/closure-compiler/compiler-latest.zip)
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:
* 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.
10
13
11
14
## Options for Getting Help
@@ -17,29 +20,41 @@ The [Closure Compiler](https://developers.google.com/closure/compiler/) is a too
17
20
18
21
Note: The Closure Compiler requires [Java 7 or higher](http://www.java.com/).
19
22
20
-
### Using [Ant](http://ant.apache.org/)
23
+
### Using [Maven](http://maven.apache.org/)
21
24
22
-
1. Download the [Ant build tool](http://ant.apache.org/bindownload.cgi).
@@ -115,10 +130,21 @@ will re-order the inputs automatically.
115
130
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).
116
131
2. Make sure someone hasn't requested the same thing. See the list of [known issues](https://github.com/google/closure-compiler/issues).
117
132
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).
118
-
4. Submit your reqest as an issue.
133
+
4. Submit your request as an issue.
119
134
120
135
### Submitting patches
121
-
1. All contributors must sign a contributor license agreement. See the [CONTRIBUTORS](https://raw.githubusercontent.com/google/closure-compiler/master/CONTRIBUTORS) file for details.
136
+
1. All contributors must sign a contributor license agreement (CLA).
137
+
A CLA basically says that you own the rights to any code you contribute,
138
+
and that you give us permission to use that code in Closure Compiler.
139
+
You maintain the copyright on that code.
140
+
If you own all the rights to your code, you can fill out an
If your employer has any rights to your code, then they also need to fill out
143
+
a [corporate CLA](http://code.google.com/legal/corporate-cla-v1.0.html).
144
+
If you don't know if your employer has any rights to your code, you should
145
+
ask before signing anything.
146
+
By default, anyone with an @google.com email address already has a CLA
147
+
signed for them.
122
148
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)
123
149
3. Fork the repository.
124
150
4. Make your changes.
@@ -226,12 +252,12 @@ options/arguments in your CUI application.</td>
0 commit comments