Gradle: Difference between revisions
Content added Content deleted
Altilunium (talk | contribs) (Created page with "{{Cquote|Gradle started as an open-source project in 2008 led by Hans Dockter and Adam Murdoch. The success of the Gradle Build Tool project ultimately led to the development of Gradle Enterprise which was launched in 2017||| Gradle Enterprise "[https://gradle.com/our-story/ Our Story]"}} {{Cquote|My original idea was to call it Cradle. The disadvantages of that name were too diminutive and not very unique. As it is using Groovy for the DSL, I went down the G-road and t...") |
Altilunium (talk | contribs) No edit summary |
||
| Line 2: | Line 2: | ||
{{Cquote|My original idea was to call it Cradle. The disadvantages of that name were too diminutive and not very unique. As it is using Groovy for the DSL, I went down the G-road and though about calling it Gradle. Everyone I asked liked it, so that became the official name. That was about 4 years ago. I'm still very happy with the name||| Hans Dockter (December, 2011) "[https://discuss.gradle.org/t/why-is-gradle-called-gradle/3226 Why is gradle called gradle?]" discuss.gradle.org}} |
{{Cquote|My original idea was to call it Cradle. The disadvantages of that name were too diminutive and not very unique. As it is using Groovy for the DSL, I went down the G-road and though about calling it Gradle. Everyone I asked liked it, so that became the official name. That was about 4 years ago. I'm still very happy with the name||| Hans Dockter (December, 2011) "[https://discuss.gradle.org/t/why-is-gradle-called-gradle/3226 Why is gradle called gradle?]" discuss.gradle.org}} |
||
{{Cquote|Software code bases are growing in size and complexity. The build system must enable a continuous integration process for such software stacks, by connecting all of the different modules together and giving fast feedback on the correctness of any change. Without such a build infrastructure, the productivity of the software development process suffers terribly.<br><br> |
|||
The mission of Gradle is to provide a tightly integrated and super fast build infrastructure for even the largest and most complex software stacks on the planet. We want to turn Gradle into the most powerful native build system on the planet. ||| Hans Dockter (July, 2014) [https://discuss.gradle.org/t/revolutionary-new-gradle-features-on-the-2014-roadmap/7724 Revolutionary new Gradle Features on the 2014 Roadmap] discuss.gradle.org}} |
|||
Revision as of 09:49, 29 May 2023
“”Gradle started as an open-source project in 2008 led by Hans Dockter and Adam Murdoch. The success of the Gradle Build Tool project ultimately led to the development of Gradle Enterprise which was launched in 2017
|
| — Gradle Enterprise "Our Story" |
“”My original idea was to call it Cradle. The disadvantages of that name were too diminutive and not very unique. As it is using Groovy for the DSL, I went down the G-road and though about calling it Gradle. Everyone I asked liked it, so that became the official name. That was about 4 years ago. I'm still very happy with the name
|
| — Hans Dockter (December, 2011) "Why is gradle called gradle?" discuss.gradle.org |
“”Software code bases are growing in size and complexity. The build system must enable a continuous integration process for such software stacks, by connecting all of the different modules together and giving fast feedback on the correctness of any change. Without such a build infrastructure, the productivity of the software development process suffers terribly.
The mission of Gradle is to provide a tightly integrated and super fast build infrastructure for even the largest and most complex software stacks on the planet. We want to turn Gradle into the most powerful native build system on the planet. |
| — Hans Dockter (July, 2014) Revolutionary new Gradle Features on the 2014 Roadmap discuss.gradle.org |