Safe and Bullet-Proof Gradle Migration
So you think Gradle is an interesting tool? Now you're wondering how to leverage it in a highly mavenized organization? Or perhaps you work with a legacy ant build that is painful to maintain and evolve? Or maybe you just want to kickstart Gradle in your brand new project? This session will demonstrate potential patterns for migrating to Gradle from legacy maven and ant builds through live-coded examples. Changing the build system is a serious matter that can be done methodically, incrementally and in a test driven manner for stress free migration.
We will live-code a Gradle multi-project build whose one subproject is a regular maven build. We will do the same exercise with ant. This demonstrates Gradle's unique capabilities of “wrapping” existing builds and acting like a meta build system. This enables planned and incremental migration of large builds where certain components can be still built with an existing tooling. With flexibility in its DNA, Gradle can be adjusted to virtually any existing project structure and hence the legacy build can be fully operational during the transition.
About Szczepan Faber
- Humble maker of great tools for engineers
- Founder of Mockito framework, member of Shipkit team
- Core engineer of Gradle 1.x and 2.x.
- Tech Lead of Development Tools at LinkedIn
- Obsessed with software quality (via clean tests!!!) and continuous delivery (via Gradle automation!!!)
- User of GitHub, Twitter, and LinkedIn