Extend your application with pluggable Groovy DSL
summary
A plugin engine that lets teams extend Artifactory with executable Groovy DSLs compiles scripts, wraps closures into Java interfaces, and hot-loads without restart so new commands run via REST immediately; it uses Groovy metaprogramming (notably methodMissing-based DSL) and injects a public API response/context plus repository/security objects for powerful hooks into CI/CD. Java plugins are supported via classpath scanning, IntelliJ gets DSL support via Groovy descriptor files, and the system works in production (early adopters include Netflix) while dependency isolation remains a manual pain (repackage jars or use module tech).
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:18Standard API problems
- 8:16What is DSL and why
- 13:35Groovy DSL capabilities
- 20:05Java plugins: how it works
- 22:13Groovy plugins: method missing
- 26:17Public plugin API
- 32:06Security and limits
- 40:40Dependency conflicts
- 49:17Solving dependency issues
- 51:43Custom plugin examples
- 57:17Q&A
related talks
01h 27mUsing the Groovy Ecosystem for Rapid Development on the JVM
35mWhat makes Groovy a great scripting language
01h 49mInside the Gradle DSL
05mInterview
01h 29mDistributed Platform Development with Groovy
01h 15mKeeping growing software projects under control with Gradle
39mPlug-in Architectures With Layrry & Java Module System
30mGradle Ex Machina