🌀 Fastest auto complete for gradle tasks
JavaScript
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.github stalebot Feb 1, 2018
extras v1.0.7 Jun 30, 2017
.editorconfig first commit Jun 28, 2017
.gitattributes first commit Jun 28, 2017
.gitignore first commit Jun 28, 2017
.travis.yml cena Jun 30, 2017
cli.js moved the tasks file to the build folder Dec 12, 2017
license first commit Jun 28, 2017
package-lock.json moved the tasks file to the build folder Dec 12, 2017
package.json v1.3.0 Dec 12, 2017
readme.md how to achieve this terminal Jul 5, 2017
stale.yml added stale bot Jan 22, 2018
test.js first commit Jun 28, 2017
yarn.lock added offline mode Jul 3, 2017

readme.md

Gradlr

Fastest way to run your gradle tasks

Build Status npm npm

Install

$ npm install -g gradlr

Usage

$ gradlr
	Usage
		$ gradlr

	Options
		-o, --offline  Execute the build without accessing network resources
		-f, --force    Force to re-index the tasks

	Examples
		$ gradlr
		$ gradlr --force
		$ gradlr --offline

What happens under the hood?

First time you run gradlr it will cache the gradle tasks so the #2 time it'll load them instantantly. How does it know it needs to re-index? When caching, this tool saves a checksum of the sum of checksums of all of the projects' gradle files (META!), so it knows when you changed something and re-indexes when needed.

Should I commit the .tasks.cache.json file?

If you commit it, your colleagues will not have to index the tasks again.

What terminal am I using?

Since a lot of people has been asking about my terminal setup, I made this article explaining how to achieve it.

Created by

Cesar Ferreira

License

YOLO © Cesar Ferreira