To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=65977
------- Additional comments from [EMAIL PROTECTED] Thu Jun 1 02:59:45 -0700 2006 ------- I am against that debug-only enabled Java trace. Have a look at the thread: http://lists.ximian.com/pipermail/openoffice/2006-May/001826.html It would have saved me some time if there had been a trace from beginning. ;) So a more verbose RuntimeException is the only way I see. Still, it is just a Java trace like any other if some Java code fails. And I do not like to hide the traces. Makes debugging really hard. Well, just my thoughts. ;) --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
