Oops - looks like it was done as part of IO-380 (not yet released).
See also IO-381 which adds a method that does not close the input stream:
public static void copyToFile(final InputStream source, final File destination)
On 6 August 2014 19:10, Alex P wrote:
> Could you point me out.
>
> 2.4 d
Version 2.5's snapshot at
http://commons.apache.org/proper/commons-io/apidocs/index.html contains the
close portion.
-Original Message-
From: Alex P [mailto:student...@gmail.com]
Sent: Wednesday, August 06, 2014 02:11 PM
To: Commons Developers List
Subject: Re: [io] FileUtils
Could you point me out.
2.4 does not say that:
http://commons.apache.org/proper/commons-io/javadocs/api-2.4/org/apache/commons/io/FileUtils.html#copyInputStreamToFile%28java.io.InputStream,%20java.io.File%29
WBR
AlexP.
On Wed, Aug 6, 2014 at 1:55 PM, sebb wrote:
> On 6 August 2014 18:47, A
On 6 August 2014 18:47, Alex P wrote:
> Hi All,
>
> FileUtils.copyInputStreamToFile(...) closes the source InputStream, what I
> don't think is correct.
> What do you think?
The Javadoc clearly states that the source is closed.
> With best regards,
>AlexP.
--
Hi All,
FileUtils.copyInputStreamToFile(...) closes the source InputStream, what I
don't think is correct.
What do you think?
With best regards,
AlexP.
What would you have it do if the directory is null? Currently it will throw
a NullPointerException. Would it be more correct to simply do nothing (as it
does when the directory does not exist)?
On Thu, Jan 28, 2010 at 10:48 PM, shukai yuan wrote:
> HI,
>
> Maybe the method FileUtils.deleteDirect
HI,
Maybe the method FileUtils.deleteDirectory(File directory) should check
whether the directory is null?
Shukai