If you have gotten it working in Android Studio, I'd be very keen to see how (if you are willing to share).
A few months ago I had a chance to work with gradle and it looked to me like it was a step away from declarative project descriptions, back to writing loops to iterate through files, etc. Possibly I was using it wrong, but I've heard great things about it and perhaps my expectations were just too high.
Exactly why I like it. The delusion that build scripts are 100% declarative is one of those things that makes me hate tools like Ant etc. with a passion.
Parts of build scripts can be declarative, but the ability to break out and put imperative logic in some section where you need it is crucial. And the nice thing about Groovy (which Gradle is based on) is that you can usually do it in a very declarative way (eg: files*.delete() rather than looping, etc.)
Um, what? I can think of plenty of times when I've needed to edit 9patches myself. Mind you, most of those times were when I was working in a startup, and we didn't have a dedicated UI/UX person, but this feature would still be incredibly handy.
Yeah some blog posts are coming soon
Android Studio is not really usable as an IDE if you want to have a fully featured test suite because of the weird, half-implemented Gradle "auto-sync" magic (http://www.sep.com/sep-blog/2013/10/17/android-studio-not-re...). Until then, it's still good ole' reliable Eclipse (I can't believe I just said that). Until a different IDE can support Robolectric and Robotium/Instrumentation tests in the same projct that can be run/debugged inside the tool and report results in a window (command line and html test reports don't count, sorry), I won't be switching.