On Wed, 18 Oct 2006, Jeffrey Hutzelman wrote: > Yeah; that's expected. This problem is fixed in 1.4.2-final, due to be > released any moment now. Or, say, yesterday. The announcement will be forthcoming. Derrick