We were working on some refactored code today that wasn’t refactored properly. The tests had been changed to make the refactored code pass. My colleague said that I should write-up my “profound” comment on the situation:
If you’re performing a refactoring and you find yourself changing asserts in existing unit tests, something should smell bad. You’ve probably done something more than refactor the code.
T-Mobile G1/Google Android
If you haven’t got it yet, go get the Ubiquity plugin for Firefox. This is one of the coolest things I’ve seen in a long time. I think applications should have this kind of feature. Instead of navigating menus, etc. have a shortcut that takes you where you want to go or helps you do a task.
Wicket Web Beans 2.0 Features
I Will Make You Rich, Allow You to Travel the World, and You Don't Have to Do Anything!
Starting Work on WWB 2.0
Wicket Web Beans 1.0 (final) Released
WicketWebBeans 1.0-rc2 Released
The WWB subversion tree has been reorganized in preparation for the 1.0-rc2 release. The trunk now contains the Wicket 1.3.0-rc1 support and the wicket-1.3 branch is gone. The Wicket 1.2.6 support is now in the wicket-1.2.6 branch. In addition, the Java packages have been renamed from wicket.contrib.webbeans to net.sourceforge.wicketwebbeans to be more consistent with Sourceforge projects.