[udig-devel] Code clean-up

[Jesse Eichar]

Hi all,

I'm very happy to announce that we've spent the last couple weeks  
cleaning house.  As a reminder we complained recently that the unit  
tests were not being used because they were interfering with each  
other (they would pass in isolation but fail when all tests were ran  
together).  So we have spent the last couple of weeks and now all the  
tests pass and are very useable.

Second I tried out the latest 3.2 maintenance build today and it is  
much better than 3.2.0, both in speed and stability.  The official  
3.2.1 comes out in the end of next week and you will see a big jump  
in the performance of uDig when we do the next release.

Third,  we have run Find Bugs on all of the uDig plugins and fixed  
all the warnings (that make sense to fix).  As always (or almost  
always) it found a number of issues.  For example in consistent  
synchronization, incorrect double checked locking, potential null  
pointers, etc...

We want at least another week of hard-core testing/bug fixing and  
we'll put out the next release.

Cheers,

Jesse