https://github.com/angular/ng-closure-runner
https://github.com/angular/ng-closure-runner
Last synced: 9 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/angular/ng-closure-runner
- Owner: angular
- License: mit
- Archived: true
- Created: 2013-07-01T19:46:28.000Z (about 13 years ago)
- Default Branch: master
- Last Pushed: 2016-10-21T10:24:35.000Z (over 9 years ago)
- Last Synced: 2024-09-26T11:04:21.414Z (almost 2 years ago)
- Language: Java
- Size: 5.68 MB
- Stars: 12
- Watchers: 20
- Forks: 16
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# ng-closure-runner [](https://travis-ci.org/angular/ng-closure-runner)
Wraps Google Closure Compiler for AngularJS-specific compile passes
## Hacking
ng-closure-runner is a lightweight runner around the
[Google Closure Compiler](https://developers.google.com/closure/compiler/). For
a complete description of how Closure Compiler works, refer to the
[source code](https://code.google.com/p/closure-compiler/source/browse/) and
[javadoc](http://javadoc.closure-compiler.googlecode.com/git/index.html). Refer
to `src/org/angularjs/closurerunner/MinerrPass.java` as an example of how to
write a custom compiler pass.
We use [Gradle](http://www.gradle.org) to build. You'll need a current JDK
(version 1.6 or higher). To compile and run the tests:
```
$ gradle check
```
Submissions should include corresponding tests.
## Releases
Releases should be handled by the core Angular team.
To create a new release:
1. Run `gradle distZip`.
2. Commit the updated file in `assets/ng-closure-runner.zip`
3. Create a tag pointing to the commit.
4. In Angular, update the reference in `bower.json` to use the new tag.
5. That's it! You're done.