The Apache Wicket team is proud to announce the availability of the first maintenance release: Apache Wicket 1.3.1.

A lot of bugs have been squashed and improvements implemented. The most notable improvement is the addition out-of-the-box, transparent clustering support.

1.3 has personally been extremely stable and a ton of features that if you are still using 1.2 you should bite the bullet and jump.

 Apache Wicket

 The Apache Wicket team is starting off 2008 with a bang.  They just officially released version 1.3!  This is great to see since I have been personally using 1.3 codes since last year and have had very little stability issues related to the framework.  Just goes to show how well Wicket is built/designed and the team behind it!

http://wicket.apache.org/

If you don’t know what Wicket is, then you must not have talked to me, since it is the only Java web framework I will talk about anymore!

Be come a Wicket fanatic and see how Java web development should have been done for years.

Great work Wicket team… I look forward to what 1.4 brings and the migration to Java 5 and generics…. Yes!

Being quite the Wicket slut these days, I have to admit that a book about my favorite web  framework is exciting to see.  It reinforces what I already know, Wicket rocks!

The authors are two of the projects very active committers.

Martijn Dashorst and Eelco Hillenius

I have been on the Manning MEAP program for it and the book is looking very good.  It will be great to point newbs at on what Wicket it can do.

I know personally I have created web pages quicker, with more function than ever before in a java framework.  In comparison to my days back in Struts (oh the pain), once you get your head around Wicket, it is just sweet.

It truly makes web development in Java fun again.

Long live Wicket.

I have seen the gambit of frameworks, technologies, features, whatever.

Well I have to say, I have seen the future of Java Web development and it is called Wicket.

If you do any Java web development, you MUST investigate Wicket.

http://wicket.apache.org

I will never write another JSP page as long as I do Java web development.

We had C, we made it better by C++.

We had C++, we made it better by Java.

We had Pascal, we made it better by ObjectPascal.

We had ObjectPascal, we made it better(?) by .Net.

(You can skip the whole C#, VB.Net, etc)… its still all .Net.

So…

We have Java & .Net, we make it better by Scala?

Is Scala really the next Java & .Net replacement?

Tate Needham over at VSoft Technologies hit the nail on the head with a post: “Who cares if the build is broken?”

“If the development team is serious about creating quality software, then the entire team should care about the build being broken. Even if the team does not use any sort of continuous integration practices, a broken build is never a good thing.”

I know I have seen it time and time again when a team gets buy in by say 90% of the team and everything is going great. But then there is that one day when the other 10% of the team thinks automated builds are a waste of time and money. Those are the folks that ignore the emails about the build being broken. Better yet, they are the folks that yell from the mountain top the WOMB (works on my box) mantra.

“Oh I have to check in the library too for the build to work!”

Playing dumb on a development team never really pays off now does it!

It was based on the write up by Derick over at AvacodoSoftware.com: The Build Is Broken… Who Cares?