[Gradle 도전기] 2. Overview

[Gradle UserGuide 도전기] 2. Overview

---

  2.1 Features

---

  쭉 읽어봤는데 대충 눈에 들어오는 내용은

1. Groovy 기반으로 만들어서 Java 개발자가 쉽게 만들 수 있음

2. Multi-Project를 build하기에 좋음

3. 다양한 방법으로 의존성 관리를 할 수 있음

4. 다른 툴과의 통합이 가능

5. 다른 툴과의 Migration이 쉬움

6. Gradle Wrapper의 존재로 실행하는 머신에 굳이 Gradle이 안깔려도 됨

  등이 눈에 들어온다. 다 그냥 이래서 좋다. 저래서 좋다. 인 듯 ? 아 그리고, 공짜다.

다음은 원문이다. 위에 제시한 번호와 아래 번호는 관련이 없다. 

1. Declarative builds & build-by-convention

  At the heart of Gradle lies a rich extensible Domain Specific Language (DSL) based on Groovy. Gradle pushes declarative builds to the next level by providing declarative language elements that you can assembleas you like. Those elements also provide build-by-convention support for Java, Groovy, OSGi, Web and Scala projects. Even more, this declarative language is extensible. Add your own new language elements or enhance the existing ones, thus providing concise, maintainable and comprehensible builds.

2. Language for dependency based programming

  The declarative language lies on top of a general purpose task graph, which you can fully leverage in your builds. It provides utmost flexibility to adapt Gradle to your unique needs.

3. Structure your build

  The suppleness and richness of Gradle finally allows you to apply common design principles to your build. For example, it is very easy to compose your build from reusable pieces of build logic. Inline stuff where unnecessary indirections would be inappropriate. Don't be forced to tear apart what belongs together (e.g. in your project hierarchy). Avoid smells like shotgun changes or divergent change that turn your build into a maintenance nightmare. At last you can create a well structured, easily maintained, comprehensible build.

4. Deep API

  From being a pleasure to be used embedded to its many hooks over the whole lifecycle of build execution, Gradle allows you to monitor and customize its configuration and execution behavior to its very core.

5. Gradle scales

  Gradle scales very well. It significantly increases your productivity, from simple single project builds up to huge enterprise multi-project builds. This is true for structuring the build. With the state-of-art incremental build function, this is also true for tackling the performance pain many large enterprise builds suffer from.

6. Multi-project builds

  Gradle's support for multi-project build is outstanding. Project dependencies are first class citizens. We allow you to model the project relationships in a multi-project build as they really are for your problem domain. Gradle follows your layout not vice versa.

  Gradle provides partial builds. If you build a single subproject Gradle takes care of building all the subprojects that subproject depends on. You can also choose to rebuild the subprojects that depend on a particular subproject. Together with incremental builds this is a big time saver for larger builds.Page 24 of 443

7. Many ways to manage your dependencies

  Different teams prefer different ways to manage their external dependencies. Gradle provides convenient support for any strategy. From transitive dependency management with remote Maven and Ivy repositories to jars or directories on the local file system.

8. Gradle is the first build integration tool

  Ant tasks are first class citizens. Even more interesting, Ant projects are first class citizens as well. Gradle provides a deep import for any Ant project, turning Ant targets into native Gradle tasks at runtime. You can depend on them from Gradle, you can enhance them from Gradle, you can even declare dependencies on Gradle tasks in your build.xml. The same integration is provided for properties, paths, etc ...

  Gradle fully supports your existing Maven or Ivy repository infrastructure for publishing and retrieving dependencies. Gradle also provides a converter for turning a Maven pom.xml into a Gradle script. Runtime imports of Maven projects will come soon.

9. Ease of migration

  Gradle can adapt to any structure you have. Therefore you can always develop your Gradle build in the same branch where your production build lives and both can evolve in parallel. We usually recommend to write tests that make sure that the produced artifacts are similar. That way migration is as less disruptive and as reliable as possible. This is following the best-practices for refactoring by applying baby steps.

10. Groovy

  Gradle's build scripts are written in Groovy, not XML. But unlike other approaches this is not for simply exposing the raw scripting power of a dynamic language. That would just lead to a very difficult to maintain build. The whole design of Gradle is oriented towards being used as a language, not as a rigid framework. And Groovy is our glue that allows you to tell your individual story with the abstractions Gradle (or you) provide. Gradle provides some standard stories but they are not privileged in any form. This is for us a major distinguishing feature compared to other declarative build systems. Our Groovy support is not just sugar coating. The whole Gradle API is fully Groovy-ized. Adding Groovy results in an enjoyable and productive experience.

11. The Gradle wrapper

  The Gradle Wrapper allows you to execute Gradle builds on machines where Gradle is not installed. This is useful for example for some continuous integration servers. It is also useful for an open source project to keep the barrier low for building it. The wrapper is also very interesting for the enterprise. It is a zero administration approach for the client machines. It also enforces the usage of a particular Gradle version thus minimizing support issues.

12. Free and open source

  Gradle is an open source project, and is licensed under the ASL.

  2.2 Why Groovy?

---

 그루비를 선택한 이유는 간단하다. 자바 개발자들에게 XML보다 훨씬 명료하게 build scripts를 제공하기 위해서이다.

We think the advantages of an internal DSL (based on a dynamic language) over XML are tremendous when

used in build scripts. There are a couple of dynamic languages out there. Why Groovy? The answer lies in the

context Gradle is operating in. Although Gradle is a general purpose build tool at its core, its main focus are

Java projects. In such projects the team members will be very familiar with Java. We think a build should be as

transparent as possible to all team members.

In that case, you might argue why we don't just use Java as the language for build scripts. We think this is a

valid question. It would have the highest transparency for your team and the lowest learning curve, but because

of the limitations of Java, such a build language would not be as nice, expressive and powerful as it could be. [1]

Languages like Python, Groovy or Ruby do a much better job here. We have chosen Groovy as it offers by far

the greatest transparency for Java people. Its base syntax is the same as Java's as well as its type system, its

package structure and other things. Groovy provides much more on top of that, but with the common foundation

of Java.

For Java developers with Python or Ruby knowledge or the desire to learn them, the above arguments don't

apply. The Gradle design is well-suited for creating another build script engine in JRuby or Jython. It just

doesn't have the highest priority for us at the moment. We happily support any community effort to create

additional build script engines.