[jira] Updated: (IO-34) [io] FileSystemUtils returns incorrect free space on Linux

[ http://issues.apache.org/jira/browse/IO-34?page=all ] Stephen Colebourne updated IO-34: - Bugzilla Id: (was: 38574) Fix Version: 1.2 Final Version: 1.1 Final (was: 1.1.0) > [io] FileSystemUtils returns incorrect f

[jira] Closed: (IO-34) [io] FileSystemUtils returns incorrect free space on Linux

[ http://issues.apache.org/jira/browse/IO-34?page=all ] Stephen Colebourne closed IO-34: Resolution: Fixed > [io] FileSystemUtils returns incorrect free space on Linux > -- > >

[jira] Reopened: (IO-34) [io] FileSystemUtils returns incorrect free space on Linux

[ http://issues.apache.org/jira/browse/IO-34?page=all ] Stephen Colebourne reopened IO-34: -- Reopening to change versions > [io] FileSystemUtils returns incorrect free space on Li

DO NOT REPLY [Bug 38574] - [io] FileSystemUtils returns incorrect free space on Linux

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 38574] - [io] FileSystemUtils returns incorrect free space on Linux

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 38574] New: - [io] FileSystemUtils returns incorrect free space on Linux

gzilla/show_bug.cgi?id=38574 Summary: [io] FileSystemUtils returns incorrect free space on Linux Product: Commons Version: 1.1.0 Platform: Other OS/Version: other Status: NEW Severity: normal Priori

Re: [io] FileSystemUtils

Most I/O developers are used to deal with "byte[]"s, "int"s and "long"s in a very strict way. It seems to me that the "long" version of freeSpace() should really exist to fit more strict needs. I was wondering what would be the result of a FileSystemUtils.freeSpace() call over a path with 2GB+ fre

Re: [io] FileSystemUtils

Would there be, or should I ask, how strong, objections to just changing it to return BigInteger, period? No overloaded versions, no artificially-meaningful (although perfectly reasonable) "special" values, etc.? I know it's a change to the public interface and that's not generally something that

Re: [io] FileSystemUtils

This should be raised as a bug in bugzilla, as the existing code will just break if the free space is too large. I propose it should return -1 if the free space is too large. To deal with large drives, we should add either a BigInteger returning method, or a freeSpaceMB method (that returns th

Re: [io] FileSystemUtils - Unix Test failing on Gump

Niall Pemberton wrote: Gump is failing for IO at the moment: http://vmgump.apache.org/gump/public/jakarta-commons/commons-io/gump_work/build_jakarta-commons_commons-io.html From a scan of the source, looks like the following is happening when FileSystemUtilsTestCase.testGetFreeSpace_String()

[io] FileSystemUtils - Unix Test failing on Gump

Gump is failing for IO at the moment: http://vmgump.apache.org/gump/public/jakarta-commons/commons-io/gump_work/build_jakarta-commons_commons-io.html >From a scan of the source, looks like the following is happening when FileSystemUtilsTestCase.testGetFreeSpace_String() is run on Unix with a path

Re: [io] FileSystemUtils constructor

Ok, cool, I didn't know non-private constructors was a general requirement. Thanks for the heads-up. Frank Stephen Colebourne wrote: Frank W. Zammetti wrote: As was pointed out to me by a user, I mistakenly wrote the constructor of the FileSystemUtils as public, where it whould be private a

Re: [io] FileSystemUtils constructor

Frank W. Zammetti wrote: As was pointed out to me by a user, I mistakenly wrote the constructor of the FileSystemUtils as public, where it whould be private as it is suppoed to disallow instantiation of the classm as the comment says... just a brainfart I guess :) Unless anyone thinks it shou

[io] FileSystemUtils constructor

As was pointed out to me by a user, I mistakenly wrote the constructor of the FileSystemUtils as public, where it whould be private as it is suppoed to disallow instantiation of the classm as the comment says... just a brainfart I guess :) Unless anyone thinks it should be left public in case

[io] FileSystemUtils fixes

Hi all, Bugzilla ticket 36325 includes an updated version of FileSystemUtils that addresses the two outstanding issues: (1) It should now work on all Windows language versions, although I only have an English version to test with... since it no longer looks for any particular string I fully expec