-To be defined-

It’s been more than a week since I had my last beer at Bier Central and left Antwerp with great memories and even greater amount of inspiration.

This won’t be a regular blog post about Devoxx and talks that I have attended. This can wait a little longer on my tremendously long backlog. At Metropolis you can obviously hear about all the exciting new things (and I don’t necessarily mean lambdas) or even listen to crazy DJ set entirely composed (live!) using Clojure and Emacs.

Instead I would like to share with you how it really is to be there.

I must admit I’m not really a huge fan of Maven, but I’m not going to rant how much maven sucks in this post. This tool brought quite a bit of good things to the build automation landscape in Java. Instead I will share with you how to make it a bit more pleasant to use. It’s still de facto a standard in open source world so I guess I will keep it in my toolbox for a little longer.

Being a good citizen of the open source community means following the rules concerning software development defined by the team. One of them, sadly the one very frequently neglected, is meaningful commit message with a reference to the task you worked on. Such an info can be later leveraged by tools like FishEye, but that’s another story. So what’s the problem with that for lazy guys like me?