The Stumble Stones
The Android Team’s switch from the Eclipse based Android Developer Tools to the IntelliJ IDEA based "Android Studio" at Google I/O is pretty well-known. But what isn’t too well-known is that they also changed the default android project directory structure as they switched their build system from ant to gradle.
Further information on the new structure and the new build system are available here: http://tools.android.com/tech-docs/new-build-system/user-guide
I decided to go with the new Gradle-based structure as I thought it was more future proof. I have to admit that I regret this badly! As I’m not too familiar with Gradle, yet, I had a pretty bad time trying to understand the customizations brought in by the gradle-android plugin. Additionally most of the information available on the net is specific to Eclipse/ Ant based projects and therefore slightly different for the new structure.
As I apparently love to use many braces in my blog posts, Clojure is just a natural match! ;) Just kidding. I wanted to dig into Clojure for about a year now, but couldn't find the time. Clojure to me seems like the most interesting member of the functional programming language family.
… but there is also this one: http://clojure-doc.org/
… and even this one: http://clojuredocs.org/
… and additionally there's the official documentation at http://clojure.org/documentation ;-)
Lately I was granted the "Collaborator" status on the Sonar Plugin for IntelliJ IDEA at Github (https://github.com/gshakhn/sonar-intellij-plugin/) and I'd like to share with you the benefits of this project.
For those who aren't familiar with the benefits of Sonar's source code analysis, yet, you should really take a look. Sonar not only performs CheckStyle, PMD and FindBugs analysis of your code and highlights the validations on the specific lines of code. But by leveraging the power of JaCoCo Code coverage it is also able to determine the line- and branch-coverage of your JUnit-Tests.
At this year's JavaOne I attended a talk by Marius Bogoevici (@mariusbogoevici) and was once again pointed at the JBoss Forge project. Last time I took a look at Forge it was still called Seam Forge which was about a year ago. It seriously matured since then.
JBoss Forge is a shell for rapid-application development at a command-line level. It supports developers setting up Java applications by reducing the need to write boilerplate code. In case you ever have to start a project from scratch you should really take a glance at JBoss Forge as it makes life easier!