Spring releases: getting our act together

After SpringSource's announcement that they're putting a cap of 3 months on community maintenance releases, and the expected reactions, it looks like it's not as bad as some people assumed.

If the bug fixes are applied to the public source tree at all times, as confirmed by Mark Brewer, then all we need to do is organise an 'official' community effort to build the maintenance releases between the 3 months and the next major release by SpringSource. We do want to avoid the 'many different crazy versions of Spring' that Daniel Gredler is warning us about.

Let's face it, it's not like the open source community is contributing that much to Spring anyway, by choice or not. Well SpringSource has now given the community the perfect excuse to contribute something, if not to the code base then at least to the community itself.

Now the question is, who is willing to take the lead on such a project?

java.lang.NullBlogException is back!

/**
 * Copyright 2008 Daniel Farinha. Some Rights Reserved.
 * This work is licenced under a Creative Commons Licence.
 * See http://creativecommons.org/licenses/by-nc-nd/3.0/ for the full license.
 */
package java.lang;

/**
 * @author Daniel Farinha
 */
public class NullBlogException extends Exception {
	// TODO: everything
}

It's been a while since I last blogged. According to my last entry in java.blogs it's been 2 years, 7 months and 25 days to be exact :)

I've just moved to Macau where I plan to settle down with my fiancee, so I'm now kicking into action a number of projects that I had in an ever growing TODO list. Re-lauching this blog was one of them.

Over the next few weeks and months I expect to fill this space with all things Java, especially as another of my projects is to finally work my way up the Java Certification tree, starting with the SCJP.