Bill Barker wrote: [snip] > > As Stefan pointed out at the beginning of this thread, it isn't a drop in > replacement. The [io] team has deliberately broken all backwards > compatibility.
... and as we pointed out, this has absolutely *no* effect on already compiled code. And we care *a lot* for this. And therefore it *is* a drop in replacement. In case of FileUtils, you can use for compilation now either the method without the encoding parameter or by casting for the corner case where you explicitly pass null as a constant. > That is why I'm sticking to my statement that will never > use > [io] ever again in my day job, and will recommend guava instead. Oh, well, then you should avoid also to use the JDK at all. Similar situation arise for new StringBuffer(null); this compiles with JDK 1.4.2, but is ambiguous in JDK 1.5. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
