To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=81973
------- Additional comments from kast...@openoffice.org Wed Aug 5 16:14:19 +0000 2009 ------- @milek_pl In my experience, your suggestion: "Why would you set it at installation time, and not in the Jar manifest? You can simply bundle all necessary jars in your extension and use two attributes in the manifest file: class-path and uno-type-path." simply doesn't work on OOo 3.x. The library jar files are simply not found no matter what you put in the manifest. If this worked, it would be a satisfactory solution to this issue in my mind. This way, your extension is self-contained and the dependencies are under the control of the extension developer (i.e. the user doesn't have to keep some system-wide dependency up to date whenever you change the extension.) --------------------------------------------------------------------- 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: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
