Hi,

On Sat, Feb 14, 2009 at 1:17 PM, Jukka Zitting <jukka.zitt...@gmail.com> wrote:
> org.apache.commons.io:
> Bad
> method org.apache.commons.io.FileUtils.copyFileToDirectory(java.io.File,
> java.io.File): type void in io-1.4, but type java.io.File in io-trunk
> method org.apache.commons.io.FileUtils.copyFileToDirectory(java.io.File,
> java.io.File, boolean): type void in io-1.4, but type java.io.File in
> io-trunk

I reopened IO-157 that introduced the new return value.

> org.apache.commons.io.output:
> Bad
> method org.apache.commons.io.output.NullWriter.append(char): throws
> java.io.IOException in io-1.4, but doesn't throw java.io.IOException
> in io-trunk
> method org.apache.commons.io.output.NullWriter.append(java.lang.CharSequence):
> throws java.io.IOException in io-1.4, but doesn't throw
> java.io.IOException in io-trunk
> method org.apache.commons.io.output.NullWriter.append(java.lang.CharSequence,
> int, int): throws java.io.IOException in io-1.4, but doesn't throw
> java.io.IOException in io-trunk

These don't break binary compatibility, and I don't believe that there
is any affected source code out there (the affected code would be
explicitly equivalent to a no-op).

BR,

Jukka Zitting

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to