Gradle project sync failed in Android Studio ?
Step 1. Download the latest Gradle distribution
2. STEP Releases
Here you can find binaries and reference documentation for current and past versions of Gradle. You may find release candidates and nightly builds on their respective pages.
You can install Gradle through various other tools, or download a ZIP using the links on this page.
Command-line completion scripts for bash and zsh can be downloaded from the gradle-completion project page.
Getting Started Resources
The Gradle team offers free introductory training and advanced training courses bi-monthly.
There are many Gradle tutorials available to help you get started quickly. Source distributions also include many working samples for which guides are not yet written.
v4.9
- Download: binary-only or complete
- User Manual
- API Javadoc
- DSL Reference
- Release Notes
v4.8.1
- Download: binary-only or complete
- User Manual
- API Javadoc
- DSL Reference
- Release Notes
v4.8
- Download: binary-only or complete
- User Manual
- API Javadoc
- DSL Reference
- Release Notes
v4.7
- Download: binary-only or complete
- User Manual
- API Javadoc
- DSL Reference
- Release Notes
v4.6
- Download: binary-only or complete
- User Manual
- API Javadoc
- DSL Reference
- Release Notes
Trusted by millions of developers
Gradle has been counted in the top 20 open-source projects and is trusted by millions of developers to build software for billions of people.
Performance
Incremental Builds
Gradle checks in between build runs whether the input, output or an implementation of a task has changed since the last build invocation. If not, the task is considered up to date and is not executed. Gradle also considers the configuration of the task as part of its input.
Task Output Caching
If a task has already been executed on another computer, Gradle can skip the execution locally, and instead load the task's outputs from the build cache. The typical use case is to let CI builds push to a shared build cache, and allow developers to pull from it. A local build cache is also available to reuse task outputs produced earlier on the same machine.
Incremental Subtasks
When Gradle discovers that the input or output of a task has changed between build runs, the task is executed again. The task can use the incremental API to learn what files exactly have changed. With this information the task may not need to rebuild everything.
Compiler Daemon
When you need to fork the compilation process, Gradle creates a daemon process that is reused within a multi project build. This provides a dramatic speed improvement for the compilation process.
Parallel Execution
Gradle allows parallel execution of tasks and intra-task work through a Worker API. Parallelism is very fine-grained, resulting in faster performance.
Parallel Download of Dependencies
Gradle will download both dependency metadata (typically `pom.xml`) and artifacts in parallel. This is done on demand, only when the artifacts are actually required.
Build Scans
Web-based Build Visualization
Understand what happened in your build via a rich web interface instead of a text console and text files. Build scans provide more information, more effectively.
Collaborative Debugging
Share build scans with colleagues to efficiently solve problems and improve things together. Share entire scans or links focussed to a particular aspect of the build such as a logging output line.
Compare Builds
Build scan comparison quickly highlights differences between builds, such as dependencies and their versions, making root cause analysis much faster.
Extend and Customize
Add your own data to build scans as tags, values and links. Integrate build scans into your toolchain.
Track and Export History Across all Builds
Track key build metrics for all of your builds, including local development builds and not just CI builds. Understand trends and export build scan data to storage of your choosing.
Command-Line Interface
Task Exclusion
You can exclude any task from being run. When you exclude a task, all tasks this task depends on are also automatically excluded if they have no other dependencies.
Continuous build
When a Gradle task is run in continuous mode, Gradle automatically watches for changes of the input of this task. Whenever the input changes, the task it automatically executed. You can run multiple tasks continuously in a multi-project build.
Composite builds
You can combine separate builds to work on code across multiple repositories.
Dry Run
Run a build to see which tasks actually get executed without executing the task actions.
Continue Execution After Failures
Does not stop as soon as the first failure is encountered. Executes every task to be executed where all of the dependencies for that task completed without failure. Enables discovery of as many failures as possible in a single build execution with a very nice aggregated error report at the end.
Sync Dependency Cache with Repository
Gradle has a `--refresh-dependencies` option to ignore all cached entries for resolved modules and artifacts. A fresh resolve will be performed against all configured repositories, with dynamic versions recalculated, modules refreshed, and artifacts downloaded. However, where possible Gradle will check if the previously downloaded artifacts are valid before downloading again. This is done by comparing published SHA1 values in the repository with the SHA1 values for existing downloaded artifacts.
(NOTE -: CONTANT BY GRADLE.ORG)
No comments:
Post a Comment