Log of the #nice channel on irc.freenode.net

Using timezone: Central European Time
* bonniot leaves02:35
* arjanb leaves02:47
* ArtemGr joins09:02
* bonniot joins09:51
<CIA-6>03artemgr * 10Nice/src/nice/tools/unit/api.nice: Custom classloader.10:27
03artemgr * 10Nice/src/nice/tools/unit/console/main.nice: An option to invoke System.exit when finished.10:28
<bonniot>hi artem10:57
what gives?
<ArtemGr>encountered class ordering problems twice recently. one with NiceTee - this one is hard to solve correctly, as you said, although can be partly mitigated with interface dispatch optimization. another when overriding TestListener from nice.tools.unit, this one solved with automatic jars ordering by File.lastModified() in classloader...11:00
<bonniot>you have a custom front-end of niceunit?11:38
<ArtemGr>just a "for( pkg : packages ) runTests( pkg, listener, classloader: loader );" on a predefined set of packages inside the program11:39
<bonniot>i see11:47
i wonder if garbage collecting the classloaders would release the locks
it depends on the database connector design, i guess11:48
<ArtemGr>it wont, since databases tend to start threads
* arjanb joins
<bonniot>isn't it a flaw in the connector design? what if you really need several claasloaders?11:49
<ArtemGr>well, everything would be fine if i will close the database in every test. but why should i? the application usually reuses the opened database, it is natural to do the same in the tests. the JIT might be faster with a single classloader too, perhaps. execution time of the tests is important thing in TDD, after all.11:53
<bonniot>true11:55
hello arjan11:56
<arjanb>hi12:01
<ArtemGr>salute, arjan12:02
* ArtemGr leaves15:22
* ArtemGr joins15:26
* ArtemGr leaves15:34
* ArtemGr joins15:38
* ArtemGr leaves15:39
* ArtemGr joins15:40
* ArtemGr leaves15:41
* ArtemGr joins15:43
* ArtemGr leaves18:40
* bonniot leaves23:13
* arjanb leaves23:44