In this post we look at how we can use SBT's source generators to centrally manage library dependencies across a recursive SBT build. Our aim is to have a single location where library dependencies can be managed and to then have SBT plugin code, build code and source code be able to access the centrally managed ModuleIDs.
We embrace modern DevOps practices at Cake, so we are very much of the opinion that making all servers “cattle” not “pets” is the only way to provision. However, occasionally we do need a pet, we will call him “Moose”.
Anecdotally most people in the software industry hate meetings; a meeting is a soul-sucking dementor. Jokes aside, I think it's fair to say that people feel meetings are taking too much time and the process is often painful.