Shulou(Shulou.com)06/03 Report--

This article introduces the relevant knowledge of "what are the characteristics of Gradle technology". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

Characteristics here briefly describe the characteristics of Gradle. Declarative build and contract build

The core of Gradle is domain specific language (DSL) based on Groovy, which has excellent extensibility. Gradle pushes declarative builds to a new level by providing declarative language elements that can be arbitrarily integrated. These elements also provide contract-based build support for Java, Groovy, OSGi, Web and Scala projects. Moreover, this declarative language is extensible. You can add your own language elements or enhance existing ones to provide concise, easy-to-maintain, and easy-to-understand builds.

Dependency-based programming language

Declarative language is at the top of the Universal Task Graph (general purpose task graph) and can be fully utilized in your build. It has strong flexibility and can meet some special needs of users for Gradle.

Let the structure of the building

The adaptability and richness of Gradle allow you to apply common design principles directly in your build. For example, you can easily use reusable components to make up your build. But unnecessary indirect inline content is not appropriate. Do not forcibly split parts that have been combined (for example, in your project hierarchy). Avoid making the build difficult to maintain. In short, you can create a build that is well structured, easy to maintain, and easy to understand.

API deepening

You will be more than happy to use Gradle throughout the life cycle of build execution, because Gradle allows you to manage and customize its configuration and execution behavior.

Gradle extension

Gradle extends very well. Whether it is a simple stand-alone project or a large multi-project build, it can significantly improve efficiency. This is the real structural construction. State-of-the-art build capabilities can also solve the poor build performance problems encountered by many large companies.

Multi-project construction

Gradle's support for multiple projects is excellent. Project dependency is a very important part. It allows you to simulate project relationships in multi-project builds, which is what you need to focus on. Gradle can adapt to the structure of your project, not the other way around.

Gradle provides the function of partial build. If you build a separate subproject, Gradle will build all the subprojects that the subproject depends on. You can also choose to rely on another special subproject to rebuild these subprojects. In this way, a lot of time can be saved in some large projects.

There are many ways to manage your dependencies

Different teams have different ways of managing external dependencies. Gradle provides appropriate support for any management strategy. From dependency management of remote Maven and Ivy libraries to jars or dirs of the local file system.

Gradle is the first build integration tool

Ant's tasks is a very important part of Gradle, and interestingly, Ant's projects is also a very important part. Gradle can be directly introduced into Ant projects, and Ant targets can be directly converted into Gradle tasks at run time. You can rely on them from Gradle, enhance their functionality, and even declare Gradle tasks dependencies in build.xml files. And properties, paths and so on can also be integrated in the same way.

Gradle fully supports your existing Maven or lvy repositories to construct publish or extract dependencies. Gradle also provides a converter to convert maven pom.xml files into Gradle scripts. The introduction of the Maven project at run time will also be launched later.

Easy to migrate

Gradle is compatible with any structure. So you can develop your Gradle build directly on the branch of your product build, and the two can be done in parallel. We usually recommend writing some test code to ensure that their functions are the same. In this way, the migration will not appear so messy and unreliable, which is the best practice for babies to learn to walk.

Groovy

The build script for Gradle is written through Groovy rather than XML. But unlike other ways, this is not to simply show how powerful raw scripts are in dynamic languages. Otherwise, it will only make it very difficult to maintain the build. The whole design of Gradle is developed in the direction of one language, not a rigid framework. Groovy is like glue, gluing the idea you want to achieve with the abstract Gradle. Gradle provides some standard ideas, but they do not enjoy any form of privilege. Compared with other declarative build systems, this is a more prominent feature for us.

Gradle wrapper

The Gradle wrapper allows you to run Gradle builds on machines that do not have Gradle installed. This feature will be very useful on some continuously integrated servers. It also lowers the bar for using an open source project, which means it will be very easy to build. This wrapper is also very attractive to the company. It does not need to provide corresponding management precautions for the client. This approach can also force the use of a particular version of Gradle to minimize some support problems.

Free and open source

Gradle is an open source project under the ASL license.

This is the end of the content of "what are the characteristics of Gradle technology". Thank you for your reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.