~/talk

Why you should embrace Gradle and ditch Maven

Talkat J-Fall 2018 · on Thursday, 2018-11-08
links:none on file
links:none on file
slides:none on file

Argues that Gradle replaces Maven with concrete wins: build cache (local + remote) and incremental compilation reuse task outputs to avoid rebuilding unchanged artifacts, plus a daemon and parallel workers that yield dramatic speedups (up to ~7x in best cases, only slight overhead in worst cases). Shows integrated build scans web UI for per-task timing and CI diagnostics, demonstrates migrating a real project with the Gradle Wrapper and existing plugins mostly working but notes obscure Maven plugins may need replacement. Provides commands and steps that successfully convert and run tests and CI.

AI-written summary · about

  1. 0:00Introduction
  2. 1:07Why switch to Gradle
  3. 2:15Gradle's speed advantages
  4. 4:50Declarative builds with Groovy
  5. 6:19Faster feedback in development
  6. 8:27Build scans for debugging
  7. 10:13Gradle vs Maven simplicity
  8. 12:21Maven plugin limitations
  9. 13:05Migrating from Maven
  10. 15:01Getting help and support
  11. 16:52Final thoughts
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.