I wrote a post on the innoQ blog about "Per request debugging with Log4j 2 filters".
Lately I noticed a growing dissatisfaction with my daily workflow. And this was not only because my last blog post has been almost a year ago. No, it’s related to a noticable drop in productivity. I figured this was due to my curiosity dragging me onto way more interesting topics than either my time frame or my toolset could master. Unfortunately trying to keep up-to-date on those topics created loads of distractions which almost resulted in an inability to focus on a single task for a longer amount of time
Lucky me, I’m surrounded by a bunch of awesome people whom I could talk to about this and my pending decisions.
So, what does it mean?
First of all I’ll try to get over that "writer’s block" and write small posts like this one about things on my mind.
Second of all I will have to reduce the quantity of my output on Twitter and skip some of my projects to achieve a level of quality that is finally satisfactory for me personally.
Regarding the toolset I decided to give DayOne another try. It’s a journal/ diary app that supports MarkDown (yes, I’d favor Asciidoc), syncs via iCloud, reminds me of stuff and has a few other nice features. The only downsides are it’s Apple-only and it doesn’t support WebDAV-sync which would allow automatic publishing to my blog.
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.
This event will take place in Duesseldorf on Oct, 8th 2013. It is a meetup of the German Oracle customers using Oracle middleware products. The event will feature a number of great talks around GlassFish 4.0.
I'm very happy to announce that one of my proposals for JavaOne 2013 has been accepted. This year's JavaOne takes place from Sep 22 until Sep 27 in San Francisco and will be another great chance catch up with the latest and greatest in java development and of course to meet with many old and new friends.
I'll be giving another talk on "Enterprise Application Integration Patterns and Best Practices" (CON7969). As soon as the Content Catalog is made available to the public, the session details can be found here.
Another reason I'm very excited about JavaOne is that my dear innoQ colleague Thomas Eichstädt-Engelen will join me on the trip. He and his friend Kai Kreuzer will present their OpenSource project OpenHAB - an OSGi based home automation bus system providing adapters for most of the proprietary formats and protocols on the market. With this software a smarthome becomes available to everyone.
So if you didn't checkout OpenHAB already, you should!
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.
I have been invited to talk at Java Forum Stuttgart on July 4th 2013. Java Forum is a single day event fully packed with good talks on various topics. You can see the complete schedule here. If you like to attend the event, you can register here.
My talk on "Enterprise Integration Patterns - Best Practices for application integration" will be in slot D7 from 16.40 - 17.25.
As you might have read in my previous blog post I'm currently doing Proof-Of-Concepts on what is possible with Java on a tablet like the Google Nexus7 device meaning a Nvidia Tegra chip which itself is an ARMv7 processor.
Thankfully there is a team at Ubuntu which dedicates its work to bringing a desktop linux to the tablet which supports the well-known standardized Java Runtime Environments out there.
In this blog post I describe how to setup Ubuntu Linux and Oracle Java on my newly acquired Google Nexus7 device. This shall be the foundation to checkout the things you can do with JavaFX on a Tablet computer.
My environment is a Macbook Pro (MBP) running on OS X 10.8 (Mountain Lion). The Nexus 7 (in my case the 16gb version) is attached to the MBP via its USB cable.
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!