For the last week or so I’ve worked my way through about half of Pragmatic Version Control using Git with a mixture of excitement and terror. In random order, as it comes from my mind, are some thoughts:
Just recently we attempted to update an Ant script which we are using to do automated deployments to Glassfish v2 servers, to deploy to our new Glassfish v3 servers instead. Here are some things we learned!
One thing we do is for every main hudson job we create a copy just to run the tests for a particular developer. It solves the "it runs on my machine" dilemma and frees up the developer to get on with other work.
SpringJob can be given the name of any Runnable defined within Spring and it will run it. Any exceptions will be reflected in the state of SpringJob, and this can be used to trigger another job such as an email, or it can be used in a retry timer.
The current version of expectations (1.4.3) contains support for freezing time within an expectations scenario. I already put this information out in a previous blog entry, and I'm going to use the same examples here.
For various reasons I seem to end up writing a lot of code that fiddles with the context class loader in order to get non-module code running in the OSGi environment that JDeveloper runs in. This leads to a whole bunch of code that looks like this:
Flexible programs focus on polymorphism and not inheritance. Some languages focus on static type checking (C++, Java, C#) which links the concepts and reduces polymorphic opportunities.
Languages that separate the concepts can allow you to focus on...
We recently got a post on Javalobby from a new contributor, Pavel Bernshtam. He wrote an explanation of why he thinks Groovy is a "Better Java". I was initially going to see how everyone on JL felt about...
There are several alternatives for persisting data in Android. One of those is the use of the phone's internal file system, and under certain circumstances, it can turn out to be the developer's best option.
You can use groovy in different ways - for scripting, Grails, quick prototyping, creation of DSLs etc. But I like Groovy first of all as "better Java". Really, look - almost every Java code is valid Groovy code, i.e.