To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=80100
User mux2005 changed the following:
What |Old value |New value
================================================================================
Status|CLOSED |UNCONFIRMED
--------------------------------------------------------------------------------
Resolution|INVALID |
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Fri Aug 3 10:15:35 +0000
2007 -------
Well, I am not happy with it, and if Java extensions have any practical
relevance in the marketplace (which admittedly may not be so) neither should
you. The workaround requires a change to the source code and a recompilation of
the extension. In the case of proprietary extensions that option is not
available to customers. Besides, from a technical POV I think that having the
JAR-File for the extension on the CLASSPATH is the Right Thing.
As for being able to test this:
1. Install any Java extension. You can use ours, for instance, which you can
find at http://www.projekt-limux.org/wollmux/
2. Run the BeanShell macro contained in the attached document
output_classpath_from_beanshell.odt
3. On OOo 2.2.1 you'll see that the extension's JAR file, as well as the OOo
class files from program/classes are in the CLASSPATH. On OOo 2.3 they are not.
---------------------------------------------------------------------
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]
