On Tue, Oct 19, 2010 at 12:37 AM, Jörg Schaible <joerg.schai...@gmx.de> wrote: > Hi Niall, > > Niall Pemberton wrote: > >> On Sun, Oct 17, 2010 at 4:01 PM, Jörg Schaible <joerg.schai...@gmx.de> >> wrote: >>> Hi Niall, >>> >>> Niall Pemberton wrote: >>> >>>> I have prepared Commons IO 2.0 RC5. The main changes since RC4 was to >>>> rename the FilesystemObserver/Monitor to >>>> FileAlterationObserver/Monitor and improvements to the test coverage. >>>> >>>> The RC3 changes were improvements to some tests which were causing >>>> intermittent failures in Gump & Continuum and JavaDoc improvements. >>>> For details about Continuum builds/failures, see: >>>> http://people.apache.org/~niallp/io-2.0/IOFailures.html >>>> >>>> The distro is here: >>>> http://people.apache.org/~niallp/io-2.0-rc5/ >>>> >>>> Release Notes: >>>> http://people.apache.org/~niallp/io-2.0-rc5/RELEASE-NOTES.txt >>>> >>>> Site: >>>> http://people.apache.org/~niallp/io-2.0-rc5/site/ >>>> >>>> Maven Stuff: >>>> http://people.apache.org/~niallp/io-2.0-rc5/maven/ >>>> >>>> Some Notes: >>>> >>>> * There is one error on the clirr report - which is a false positive >>>> (a generic method that is erased) >>>> http://people.apache.org/~niallp/io-2.0-rc4/site/clirr-report.html >>>> * Links to the JavaDoc versions on the site don't work (they will when >>>> its deployed to the right location) >>> >>> >>> The Sun JDKs and OpenJDK are fine, however the IMB JDKs make problems. >>> IBM JDK 1.5 does not like the OOME handling in the FileCleanerTestCase >>> and FileCleanerTrackingTestCase, while IBM JDK 1.6 has problems with the >>> WriterOutputStream handling UTF16. >> >> Hi Jörg, >> >> Thanks for testing - I logged a JIRA issue for this and put the >> details in that ticket: >> >> https://issues.apache.org/jira/browse/IO-253 > > It is good to track it. > >> The short summary is that I believe the WriterOutputStream failure is >> a bug in IBM's JDK 1.6 > > There's a good chance, IBM's JDK 1.6 is based on Apache Harmony code ;-)
I tried Harmony 6.0M3 - but the tests passed. Niall >> and the memory problems with >> FileCleanerTrackingTestCase I can't investigate because I don't have >> access to IBM JDK 1.5 > > Yeah, this is funny. For Linux you can download freely down to 1.4.2. > >> - but I believe this is an issue in the test >> rather than in FileCleanerTracking. > > The only thin that's kinda strange is that the OOME cannot be caught, resp. > it is not thrown properly. > >> It would be nice for these tests to pass on IBM's JDKs - but I don't >> think it should block the release of Commons IO 2.0. > > Fine with me. Voting is too late now ;-) > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
