The document outlines Oracle's general product direction and provides safe harbor and copyright statements. It states that the information is intended for information purposes only and should not be relied upon for purchasing decisions. Any statements regarding Oracle's plans, expectations, beliefs, intentions and prospects are forward-looking statements subject to risks and uncertainties discussed in Oracle's SEC filings. All information is current as of September 2019 and Oracle undertakes no duty to update any statements.

1. Gradle Ex Machina
Andres Almiray
@aalmiray

3. The preceding is intended to outline our general product direction. It is intended for information purposes
only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code,
or functionality, and should not be relied upon in making purchasing decisions. The development,
release, timing, and pricing of any features or functionality described for Oracle’s products may change
and remains at the sole discretion of Oracle Corporation.
Statements in this presentation relating to Oracle’s future plans, expectations, beliefs, intentions and
prospects are “forward-looking statements” and are subject to material risks and uncertainties. A detailed
discussion of these factors and other risks that affect our business is contained in Oracle’s Securities
and Exchange Commission (SEC) filings, including our most recent reports on Form 10-K and Form 10-
Q under the heading “Risk Factors.” These filings are available on the SEC’s website or on Oracle’s
website at http://www.oracle.com/investor. All information in this presentation is current as of September
2019 and Oracle undertakes no duty to update any statement in light of new information or future
events.
Safe Harbor
Copyright © 2019 Oracle and/or its affiliates.

5. pom.xml
• POM stands for Project Object Model.
• A POM file defines both how a project should be built and how
consumers may interact with the published artifacts.
• Maven delivers lots of features out of the box thanks to the
hierarchical nature of the POM.
• The Maven Super POM provides default configuration for
common plugins such as compiler, resources, surefire, etc.
• The strict nature of the structure found in the POM allows anyone
to understand the configuration.

7. build.gradle
• Gradle build files only specify how projects should be built.
• The definition for consumers is delivered through a generated
POM file.
• Gradle builds are highly customizable, resulting in a wider range
of build patterns.

8. Can we have a maven-like
structure on top of gradle?

9. Not Maven!

10. http://github.com/aalmiray/kordamp-gradle-plugins
https://aalmiray.github.io/kordamp-gradle-plugins

11. Project DSL

12. The project plugin
plugins {
id 'org.kordamp.gradle.project' version ‘0.29.0’
}
config {
release = (rootProject.findProperty('release') ?: false).toBoolean()
info {
name = 'Sample'
vendor = 'Acme'
description = 'Sample project'
links {
website = 'https://github.com/joecool/sample'
issueTracker = 'https://github.com/joecool/sample/issues'
scm = 'https://github.com/joecool/sample.git'
}
people {
person {
id = 'joecool'
name = 'Joe Cool'
roles = ['developer']
}
}
}
…
}

13. Provided behavior
• The project plugin applies the following plugins
org.kordamp.gradle.base
org.kordamp.gradle.build-info
org.kordamp.gradle.minpom
org.kordamp.gradle.jar
org.kordamp.gradle.source-jar
org.kordamp.gradle.javadoc
org.kordamp.gradle.license
org.kordamp.gradle.jacoco
org.kordamp.gradle.publishing
org.kordamp.gradle.testing
org.kordamp.gradle.apidoc
org.kordamp.gradle.source-stats
org.kordamp.gradle.source-html
org.kordamp.gradle.bintray

14. org.kordamp.gradle.base

15. Default tasks
• Gradle provides the following tasks
projects
dependencies
properties
tasks

16. Additional tasks
• The base plugin provides the following tasks
extensions
plugins
repositories
configurations
repositories
sourceSets
projectProperties
effectiveSettings
java/groovy/scala compileSettings
testSettings
publicationSettings

17. Demo

21. Additional plugins
• The following plugins can be applied explicitly
org.kordamp.gradle.kotlindoc
org.kordamp.gradle.scaladoc
org.kordamp.gradle.source-xref
org.kordamp.gradle.bom
org.kordamp.gradle.clirr
org.kordamp.gradle.guide
org.kordamp.gradle.integration-test
org.kordamp.gradle.functional-test

22. Super POM

23. The Maven super POM
• POMs are hierarchical.
• The chain resolves all the way to the top where you find the
Maven Super POM.
• Super POM configures lots of default & useful behavior.

24. The Gradle super POM
• Gradle does not offer this behavior out of the box.
• But it can be “faked” using a custom plugin.
• The plugin applies the default behavior that consuming projects
require.

25. Gradle Super POM
demo

26. File structure

27. Standard (gradle)
.
├── build.gradle
├── guide
│ └── build.gradle
├── project1
│ └── build.gradle
├── project2
│ └── build.gradle
└── settings.gradle
.
├── build.gradle
├── guide
│ └── guide.gradle
├── project1
│ └── project1.gradle
├── project2
│ └── project2.gradle
└── settings.gradle

28. Standard (gradle)
$ cat settings.gradle
include 'guide'
include 'project1'
include 'project2'
$ cat settings.gradle
include 'guide'
include 'project1'
include 'project2’
project(':guide').buildFileName =
'guide.gradle'
project(':project1').buildFileName =
'project1.gradle'
project(':project2').buildFileName =
'project2.gradle'

29. Standard (gradle)
$ cat settings.gradle
buildscript {
repositories {
gradlePluginPortal()
}
dependencies {
classpath 'org.kordamp.gradle:settings-gradle-plugin:0.29.0
}
}
apply plugin: 'org.kordamp.gradle.settings'
projects {
layout = 'standard'
}

30. Two-level (gradle)
.
├── build.gradle
├── docs
│ └── guide
│ └── build.gradle
└── subprojects
├── project1
│ └── build.gradle
└── project2
└── build.gradle
.
├── build.gradle
├── docs
│ └── guide
│ └── guide.gradle
└── subprojects
├── project1
│ └── project1.gradle
└── project2
└── project2.gradle

31. Two-level (gradle)
$ cat settings.gradle
include 'guide'
include 'project1'
include 'project2'
project(':guide').projectDir = new File(“$settingsDir/docs/guide”)
project(':project1').projectDir = new File(“$settingsDir/subprojects/project1”)
project(':project2').projectDir = new File(“$settingsDir/subprojects/project2”)
// update names if required
project(':guide').buildFileName = 'guide.gradle'
project(':project1').buildFileName = 'project1.gradle'
project(':project2').buildFileName = 'project2.gradle'

32. Two-level (gradle)
$ cat settings.gradle
buildscript {
repositories {
gradlePluginPortal()
}
dependencies {
classpath 'org.kordamp.gradle:settings-gradle-plugin:0.29.0
}
}
apply plugin: 'org.kordamp.gradle.settings'
projects {
layout = 'two-level'
directories = ['docs', 'subprojects']
}

33. Multi-level (gradle)
.
├── build.gradle
├── guide
│ └── build.gradle
└── subprojects
├── project1
│ └── build.gradle
└── project2
└── build.gradle
.
├── build.gradle
├── guide
│ └── guide.gradle
└── subprojects
├── project1
│ └── project1.gradle
└── project2
└── project2.gradle

34. Multi-level (gradle)
$ cat settings.gradle
buildscript {
repositories {
gradlePluginPortal()
}
dependencies {
classpath 'org.kordamp.gradle:settings-gradle-plugin:0.29.0
}
}
apply plugin: 'org.kordamp.gradle.settings'
projects {
layout = 'multi-level'
directories = [
'guide',
'subprojects/project1',
'subprojects/project2'
]
}

36. http://andresalmiray.com/newsletter
http://andresalmiray.com/editorial

38. Thank you!
ANDRES ALMIRAY
@AALMIRAY
ANDRESALMIRAY.COM