The document discusses the advantages of Gradle as a modern build tool for Java applications, highlighting its flexibility, powerful dependency management, and support for CI/CD processes. It contrasts traditional software development practices with modern complexities, outlining the requirements and configuration of Gradle projects. The presentation aims to encourage developers to consider Gradle for their next projects by showcasing its benefits and community support.

1. Gradle
Enterprise Build Tool

2. Hello !!
I am Deepak Shevani
- Work for Flipkart Supply Chain team
- Interests : RESTful APIs, Reactive Apps
- Contact : shevanideepak@gmail.com

3. Agenda today !!
▧ Modern Software Development
▧ Build Tools : Landscape Analysis
▧ Gradle : new Java Build Tool
▧ Why Gradle ?
▧ Demo(s)
At end of this talk, you shall decide to try
Gradle for your next project. Hopefully :)
Target

4. Traditional Software Development ??
#TraditionalUseCases
- You Write Code
- You Compile it
- You Test (Unit testing)
- You Assemble it
- You Distribute or Publish it
- You Deploy it

5. Modern Software Development ??
#ComplexUseCases
- Need Static Code Analysis
- Need Code-style checks
- Need Findbug Analysis
- Managing Dependencies
- Incremental Compilation
- Deployment Profiles
- Automated Builds
- Need Conditional Inclusion
- Need to Run Security Scans
- Need Sonar integration
- Create Docker image
:
#TraditionalUseCases
- You Write Code
- You Compile it
- You Test (Unit testing)
- You Assemble it (JAR, WAR)
- You Distribute or Publish it
- You Deploy it

6. Modern Software Development ??
#ComplexUseCases
- Need Static Code Analysis
- Need Code-style checks
- Need Findbug Analysis
- Managing Dependencies
- Incremental Compilation
- Deployment Profiles
- Automated Builds
- Need Conditional Inclusion
- Need to Run Security Scans
- Need Sonar integration
- Create Docker image
:
#TraditionalUseCases
- You Write Code
- You Compile it
- You Test (Unit testing)
- You Assemble it
- You Distribute or Publish it
- You Deploy it
#BuildTools
- Help in Automation
- Repeatable Builds
- Predictable Behavior

7. Name the build tools you know

8. Image taken from https://karussell.wordpress.com/2009/09/29/evolution-of-build-systems/

9. Focus on Java Build Tools

10. Rebel Labs Study, 2014
#Insight-1 : Almost 6
in 10 developers want
to learn more about
this build tool.
#Insight-2 : Maven is
most used build tool
and Gradle is getting
traction

11. Rebel Labs Study, 2016

12. Why Gradle ??
Groovy
Powerful & Groovy
based expressive DSL
instead of XML
Flexible
Has flexible conventions
unlike rigid conventions
in Maven
Extensible
Plugins in Gradle add
tasks, conventions and
sensible defaults
Faster
Reduced startup time
and build time using
Gradle daemons
Scalable
Incremental builds and
support for distributed
test execution
Robust
Robust and powerful
dependency management
& reproducible builds

13. Community
Several high profile
projects like Android,
Spring framework,
Hibernate etc have
migrated their build
system to Gradle. You
will find helpful
plugins for most of
the tasks.
No more boxed in :)
Unlike Maven, which is
very opinionated like
single source directory
per project, single JAR
per project, Gradle
allows you to break out
of conventions
CI/CD
Enables you to
automate many of
the tasks required to
implement CI/CD like
compile, test, deploy
and calling external
tools. Its rich CLI and
deep programming
API opens up many
opportunities.
Why Gradle ??

15. Pre-requisites
- Java JDK
- JRE
Installation
System Variables
- JAVA_HOME
- PATH
Un-packing
- Download
- Unpack
Check !!
- gradle -version
- gradle --help

16. Project Structure !!
Gradle Builds
- Has 1 or more projects
Projects
- Ex. Build JAR
- Ex. Deploy artifact
- Has 1 or more tasks
Task
- Piece of work
- Ex. Compile

17. <project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.lspe.demo</groupId>
<artifactId>demo</artifactId>
<packaging>jar</packaging>
<version>1.0-SNAPSHOT</version>
<name>demo</name>
<url>http://maven.apache.org</url>
<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<scope>test</scope>
</dependency>
</dependencies>
</project>
Build Script or build.gradle
apply plugin: 'java'
group = ‘com.lspe.demo’
archivesBaseName = ‘demo’
version = ‘1.0-SNAPSHOT’
repositories {
mavenCentral()
}
dependencies {
testCompile group: 'junit', name: 'junit', version: '3.8.1'
}
Maven Gradle
Note : Gradle builds the complete dependency
graph before any task is executed
Initialization Configuration Execution

18. Gradle Wrapper
task wrapper(type: Wrapper) {
gradleVersion = '2.7.0'
}

19. subprojects {
dependencies {
compile ‘org.twitter4j:twitter4j-core:2.2.4’
}
task copyCommonResources(type : Copy) {
from project(‘:twitter4j’).file(‘common-resources’)
into compileJava.destinationDir
}
jar.dependsOn copyCommonResources
}
Copy Resources
subprojects {
dependencies {
compile ‘org.twitter4j:twitter4j-core:2.2.4’
}
jar.doFirst {
copy {
from project(‘:twitter4j’).file(‘common-resources’)
into compileJava.destinationDir
}
}
}
Option 1 Option 2

20. test {
useJunit()
use TestNG()
jvmArgs [--‐Xmx512M]
include **/tests/special/**/*Test.class
exclude **/Old*Test.class
forkEvery = 30
maxParallelForks = Runtime.runtime.availableProcessors()}
}
// Multiple Source Directories
sourceSets.main.java.srcDirs = [ src/main/java, srcAdditional/main/java ]
sourceSets.main.java.srcDirs srcAdditionalTwo/main/java
// Multiple Test Source Directories
sourceSets.test.java.srcDirs = [ src/test/java, srcAdditional/test/java ]
sourceSets.test.java.srcDirs srcAdditionalTwo/test/java
Gradle is flexible & knows Testing

21. DEMO
Show me code !!

22. References
▧ https://docs.gradle.org/current/dsl/index.html
▧ https://zeroturnaround.com/rebellabs/java-tools-and-tech
nologies-landscape-2016/
▧ https://plumbr.eu/blog/java/how-many-java-developers-i
n-the-world
▧ http://zeroturnaround.com/rebellabs/java-build-tools-part
-2-a-decision-makers-comparison-of-maven-gradle-and-a
nt-ivy/

23. Thanks !!
You were a wonderful audience
Any questions?
You can find me at
@deepak_shevani
shevanideepak@gmail.com