Skip to content

Latest commit

 

History

History
50 lines (36 loc) · 1.5 KB

readme.md

File metadata and controls

50 lines (36 loc) · 1.5 KB

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