Colliding Branes of Quarkus
summary
Quarkus integrates Revapi to automatically detect API differences across its many modules, finds surprising breakages when upgrading libraries (example: 187 extensions and an extension bump from Flyway 1.10 → 7.3), and lets maintainers either filter internal packages or record accepted breaks in an api-changes.xml so the build stays green. The team builds a Quarkus Revapi extension that checks extension YAML/JSON, emits JSON and Asciidoc reports, and demonstrates the process: detect removals and signature changes, document or ignore them, rerun the build, and succeed.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:14Quarkx
- 5:09Demo of How Revp Works within Quarkus
- 9:19Filtering
- 20:02Dedicated Quarkx Extension for Revope
- 25:41Api Checks
related talks
50mQuarkus Unleashed
51mWhy you're missing out if you're not making Quarkus extensions
38mGitHub Automation with Quarkus
46mQuarkus why, how and what
51mQuarkus why, how and what
51mCreating Quarkus Extensions: A Practical Guide for Java Developers
45mQuarkus: Greener, Faster, Better, Stronger
49mWill my library or framework work on Quarkus (and GraalVM)?