Recently Michael Feathers wrote a blog about Open-Closed Principle, where he described simple technique that measures the closure of code. I created a Groovy script which implements this technique for Git repositories. If you run it from the root of your Git project, it produces a CSV file with the statistics of how many times files have been modified. Feel free to use this script to find hot spots in your Git repository.
When I first started working with Git in my Maven projects (three years ago), it was very awkward. Half of the release commands didn't work at all. Second half worked, but with ugly workaround via faked remote repository, which violated the entire Git philosophy.
Since then most of the issues have been resolved, including the following three which I mostly needed:
support for local Git repositories;
separation of git-commit and git-push commands in Maven release plugin;
critical bug fixes in Maven release and scm plugins.
I created a cheat sheet describing the way I typically set up and manage Git-Maven projects. Feel free to use it in your projects as well.