In-house Tapestry training by HLS

This week we are having in-house Tapestry 5 training by Howard Lewis Ship (the Tapestry creator and lead developer). The training ends with in-depth consulting on how to customize Tapestry for our own needs (e.g. using Tapestry for SMS/USSD user interfaces).

Looking forward to it!

Spring Roo - the future is bright

Couple of days ago, Ben Alex at SpringSource posted the second blog entry about Getting Started with Spring Roo. Looks really exciting, cannot wait to try it out.

Imagine the future of building LBS applications with help of Roo (and our custom plugins):

• create lbsapp (bare-bones)
  
• install webui
• install wapui
• install smsui
• install ussdui
• install billing
• install positioning
• install profile
• install map
• install revgeocode
• install mtmms

Add some glue code and you basically have MobileMap-style of an application. Now that would be pretty cool.

Tahab ehk keegi vaba tööpäeva raames seda uurida? ;-)

Welcome to JavaUba blog!

I have had the idea of starting a blog for our Java team in Regio/Reach-U already for quite some time. It is a nice way to give a publicly visible "face" to our team - share our ideas about writing Java code, development process, exciting frameworks and sometimes also some "random thoughts".

We'll see where it takes us (I hope I will not be the only one to post here).

build environment vision

Found an interesting post in blogosphere that stroke a "chord":

Now after all these years, I think I found the right solutions for Enterprise Java Builds. The solution involves 5 open source projects: Maven, Subversion, Hudson, Nexus, Sonar.

(from: The Ultimate Enterprise Java Build Solution).

For some years now, this has more-or-less also been my vision. Currently we are:

• building all new projects with Maven (with some legacy stuff still using Ant). Maven has some issues, but most of the time it works. And it seems to be getting better (eventually we might even be able to get rid of all that verbosity in our pom.xml files). I have also evaluated Gradle - it seems like a good replacement for Maven, but so far I have adopted the "wait-and-see" approach - waiting until it is used widely enough so that it would offer similar level of integration with other tools in the toolchain.
  
• happy users of Subversion (3-4 years now)
• running a Hudson-trial. I call it a "trial" because Hudson needs quite a lot of extra plugins to be used "in production" properly. And currently we do not have the time resources needed to dig deep into the plugin world of Hudson.
  
• running a Nexus-trial. Currently we are using Maven Proxy and back in December I tried to replace that with Nexus. I ran into some issues with user-authentication (it is running behind Apache httpd) and decided to wait for newer version where the security model is more pluggable (1.2, if I remember correctly). Now the newer version is out, but we currently do not have the time to dig into this again.
• not using Sonar yet but it has been on my radar for ~9 months - I have identified that it is a useful tool to have in our build environment, but have not had the time to try it out.

And then we need some extra time to integrate all those new tools with our existing tools (JIRA, Fisheye). Well, we need to assign someone to work full-time on this.

UPDATE: added comment about Gradle.