To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=80100
------- Additional comments from [EMAIL PROTECTED] Tue Aug 7 08:41:54 +0000 2007 ------- 1 It had never been specified that extension jars are put on the classpath. Extension code that relies on that behavior is thus broken. 2 Mux, why do you need an additional classloader at all when your extension "loads some classes contained in its own JAR-File"? 3 Mux, why do you think that an extension jar should end up on the global classpath? Au contraire, having dedicated classloaders for extensions improves performance and robustness. 4 See issue 51803 for background information about cleaning up the classpath, and <http://www.openoffice.org/servlets/ReadMsg?list=interface-announce&msgNo=740> for further details (esp. UNO-Type-Path; see issue 66821 on why that message is hardly readable). --------------------------------------------------------------------- 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]
