Gradle 2.breaking stereotypes.
Download as PPTX, PDF2 likes495 views
The document discusses Gradle, a flexible build tool for JVM-based projects that emerged as a competitor to Ant and Maven, emphasizing its use of Groovy for script enhancements and simplified dependency management. It covers Gradle's structure, including its support for multi-project builds, customizable plugins, and performance features like caching and a build daemon. The document also contrasts Gradle with other tools, highlighting its advantages and potential drawbacks while outlining future developments and resources for practical implementation.
Gradle 2.breaking stereotypes.
- 1. Gradle 2. Breaking stereotypes. Sergey Morenes, morenets@mail.ru March, 26 2015
- 2. About author • Works in IT since 2000 • 11 year of Java SE/EE experience • Migrated to Gradle after 7 years of Ant/Maven usage • Regular speaker at Java conferences
- 3. Agenda • Builds tools overview • Gradle under the microscope • Examples • Q & A
- 5. Magic pill
- 6. Apache Ant • Offers extreme flexibility • Imposes no convention • Lightweight dependency management
- 7. Apache Ivy • Cross-platform dependency management • Transitive dependencies • Enhanced support of repositories
- 8. Apache Maven • Offers rigid standards and support for dependency management • More difficult and inflexible standards/procedures • Declarative approach
- 9. Issue #1. XML • Large and complex files are hard to understand • Hierarchical structure limits the expressiveness of the format • Good format for the data and complex for the flow
- 10. Solution #1. Groovy • An agile and dynamic language for the Java Virtual Machine • Makes modern programming features available to Java developers with almost-zero learning curve • Provides the ability to statically type check and statically compile your code for robustness and performance • Share base syntax, type system, packages hierarchy with Java • Every Gradle build file is Groovy script
- 11. Gradle • Flexible yet model-driven JVM-based build tool • Acknowledges and improves on the very best ideas from Make, Ant, Ivy, Maven, Rake, Gant, Scons, SBT, Leinengen, and Buildr
- 12. Gradle • First release in Apr 2008 • Current version 2.3 released in February 2015 • Used in Carrier, EADS, Hibernate, Grails, Groovy, Spring-Security and Spring-Integration, Netflix, LinkedIn • Default build tool for Android OS
- 13. Hans Dockter • Founder of Gradle and Gradleware • 13 years of experience as a software developer, team leader, architect, trainer, and mentor • Previously worked at Jboss and founded Jboss-IDE • Holds a Diploma in Physics with a minor in Computer Science • Admirer of domain-driven-design
- 14. Slogan • Make the impossible possible • Make the possible easy • Make the easy elegant
- 15. Gradle overview • A flexible general purpose build tool • Declarative builds and build-by-convention plugins on top • Multi-project support • Powerful dependency management based on Ivy • Gradle is written in Java with a Groovy DSL layer on top • Programming tool • Based on Groovy
- 16. Development Version Release date Maven 1.0 2004 Maven 2.0 2005 Maven 3.0 2010 Maven 3.1 2013 Maven 3.3 2015
- 17. Development Version Release date Gradle 0.7 2009 Gradle 1.0 2012 Gradle 1.5 2013 Gradle 2.0 2014 Gradle 2.3 2015
- 18. Build structure • Gradle build consists of one or more projects • Project contains one or more tasks • Task is fundamental unit of build activity • Tasks are named collections of build instructions • Tasks are the equivalent to Ant targets • Task is made up of actions
- 19. Hello world $ gradle helloWorld
- 20. build.gradle
- 21. Maven pom
- 22. Dependencies
- 23. Dependencies
- 24. Properties
- 25. Properties
- 27. Initialization • Gradle defines which projects are involved in build • Project instance is defined for each involved project
- 28. Configuration • Task objects are assembled into an internal object model, usually called the DAG • The build scripts of all projects which are part of the build are executed • If “configuration on demand” feature is enabled then only relevant projects are configured
- 29. Execution • Gradle determines the subset of the tasks, created and configured during the configuration phase • Subset of tasks depends on the gradle command argument and the contents of the current directory. • Selected tasks are executed in the order required by their dependency relationships
- 30. DefaultTask • dependsOn(task) • doFirst(closure) • doLast(closure) • onlyIf(closure)
- 31. Sample project
- 32. Sample project
- 33. Dependent tasks
- 34. Custom task • Writes audit information at the end of the build • Audit information includes project name and build timestamp • Audit files are located in the separate folder
- 35. Custom task
- 36. Custom task
- 37. Custom task
- 38. Custom task
- 39. Multi-project builds • Build where you build more than one project during a single execution of Gradle • Sub-projects should be defined in settings.gradle • Settings file is analyzed in the initialization phase when sub-projects are revealed and included into DAG • Sub-projects are sub-directories in the simplest case
- 40. settings.gradle
- 41. Plugin • Reusable pieces of build logic • Can be used in different projects/builds • Can be written in Groovy, Java or Scala
- 42. Plugin • Add tasks to the project • Pre-configure added tasks with useful defaults • Add dependency configurations to the project • Add new properties and methods to existing type via extensions
- 43. Plugins • Android • AspectJ • Flex • Grails • GWT • JavaScript • JAXB • Jenkins • SvnKit • Tomcat • Xslt
- 44. Plugin import
- 45. Plugin portal
- 46. Plugin import
- 47. C++ support
- 48. Packaging • Build script • buildSrc project • rootProjectDir/buildSrc/src/main/groovy • Standalone project
- 49. Custom plugin
- 50. Custom plugin
- 51. Custom plugin
- 52. Custom plugin • $ gradle writeBuild
- 53. Custom plugin
- 54. Integration • Ant • Maven • Ivy
- 55. Gradle and Ant • Gradle is often described as Groovy-based Ant. • Competitor of Gant(Groovy Ant scripting) • Share DAG concept • Gradle tasks are similar to Ant targrets • Gradle variables(typeless) are close to Ant properties
- 56. Hello Ant
- 57. Ant import
- 58. Gradle and Maven
- 59. Gradle and Maven Maven Coordinate Gradle Property Gradle Default groupId group blank artifactId name Project directory name version version unspecified name N/A N/A description description null
- 60. Comparison Operation Gradle Maven Build(sec) 21,2 24,2 Inc build(sec) 8,7 11 Build with tests(sec) 29 28 Clean(sec) 3,9 3,1 Distributive(Mb) 44 3
- 61. Maven converter • Create build.gradle file in the root folder • Specify apply plugin: 'maven2Gradle' in the build.gradle file. • Run gradle maven2Gradle
- 62. Repositories • Maven and Ivy support
- 63. Maven Scope
- 64. Maven Scope Scopes: • compile • provided • runtime • test • system • import
- 65. Dependencies
- 66. Configurations • compile • default • testCompile • testRuntime • archives • runtime
- 68. Profiles • build.gradle • dev-profile.gradle • test-profile.gradle • $ gradle –Pprofile=dev build
- 71. Unit testing • Junit • TestNG • Spock • Geb • EasyB
- 72. Skip tasks • $ gradle -PskipTests
- 73. Skip tasks
- 74. Skip tasks
- 75. Caching • Gradle caches all compiles scripts by default • Compiled scripts are put into .gradle folder • Gradle uses compiled version if the script hasn’t changed • --recompile-scripts option discards cache
- 76. GUI
- 77. Daemon • Improves startup and execution time of Gradle • Initial Gradle command forks daemon process • Subsequent Gradle commands reuse the build daemon • If daemon is currently busy then new daemon process is started on-demand • Useful for small tasks execution • Expires after 3 hours of idle time
- 78. Practical tasks • Multiple projects • Liquibase • Deployment
- 79. Multiple projects • Huge project • Multiple sub-projects/pom.xml files • Complicated maintenance
- 80. Liquibase • Plugins for 2 and 3 versions • Lightweight front-end for Liquibase command-line • Gradle task for each Liquibase command
- 81. Deployment • Separate plugins for Jetty/Tomcat • General plugin for multiple containers
- 82. Cargo plugin
- 83. Cargo plugin
- 84. Pros • Native Java support • Ant/Maven integration • Full IDE support • Transitive dependency management(based on Maven/Ivy) • Multiple third-party plugins(70+) • Incremental builds • Rapid development
- 85. Cons • Less efficient and possible compilation issues due to script nature • Large learning curve • Less community & industry support
- 86. Future • Testing toolkit for integration into business logic • Improved plugin portal and plugin development • Execution of Maven builds/plugins at runtime • Distributed testing • Parallel and distributed execution … to be continued
- 87. Resources
- 88. Practice • https://github.com/hibernate/hibernate-orm • https://github.com/SpringSource/spring-framework • https://github.com/gradle/gradle
- 89. Q&A • Сергей Моренец, morenets@mail.ru