Hi, I think it would really help if the stderr of the commands that are run by GenIC/GenDD would be written to the trace to help in finding the cause for the failure. I just ran into a problem (see earlier posting), where I thought rmic had just died due to stability problems but in fact there was a problem with rmic somehow not using the correct classpath. I found that by looking at the options that rmic is called with from GenIC and then tried the same on the command line which made this obvious. I think you should really make the tools more verbose because the current way it makes tracking down errors very tedious. the same goes for catching exceptions related to failures regarding the reading of serialized DDs. just writing "cannot read ..." doesn't help as much as putting the entire stacktrace in there. just my 2c robert -- (-) Robert Kr�ger (-) SIGNAL 7 Gesellschaft f�r Informationstechnologie mbH (-) Br�der-Knau�-Str. 79 - 64285 Darmstadt, (-) Tel: 06151 665401, Fax: 06151 665373 (-) [EMAIL PROTECTED], www.signal7.de
