Issue 38324 - Adding of new JARs to SystemClasspath of javaini /rc
Summary: Adding of new JARs to SystemClasspath of javaini /rc
Status: CLOSED FIXED
Alias: None
Product: xml
Classification: Code
Component: code (show other issues)
Version: 680m52
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 1.1.5
Assignee: jogi
QA Contact: issues@xml
URL:
Keywords:
Depends on:
Blocks: 35009 35163 35170
  Show dependency tree
 
Reported: 2004-12-02 13:33 UTC by svante.schubert
Modified: 2005-06-30 12:57 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description svante.schubert 2004-12-02 13:33:14 UTC
To enable the usage of the Apache XSLT processor 'Xalan' with SO7, three of it's
JARs have to be added to the 'SystemClasspath' of the javaini/rc file.

The approach of using the 'Class-path' manifest entry to load the requrired JARs
- as done in SO8 - does not work as we are using our own classloader.

Obviously the javaini/rc file consists of two parts.
The first part after the [Install] tag is being copied by
scp/source/office/files.scp.
The latter [Java] part is most probably being added during run-time.

In setup2/source/custom/jvmsetup/jvmsetup.cxx, the 'AdditionalClasspath' of the
scp created [Install] part is being copied to 'SystemClasspath' .

But the fast forward approach, the copying of  Classpath related parts of
files.scp to scp_so/source/productpatch/productpatch.scp does not work out in
the installation.

Obviously some debugging is necessary.
Joachim Lingner, Ingo Schmidt and Dirk Voelzke gave good hints, but none could
exactly tell how the task can be accomplished. The responsible developer Markus
Herzog had left the company some time ago and the classpath handling had already
changed in SO8.
Comment 1 svante.schubert 2004-12-02 13:48:28 UTC
Adapt target to OOo1.1.5
Comment 2 svante.schubert 2004-12-16 14:05:27 UTC
Adapting the javarc/ini file by using the script particle project does not work out.
Ingo Schmidt agreed that a small C++ programm called at the end of setup (Custom
Action), which parses and add the needed classpath to the file would be the best
solution.

This task should be addressed to someone with C++ developing environment, for
whom such a task is common daily work.
Comment 3 svante.schubert 2004-12-21 21:04:03 UTC
SUS->LLA: Reassigned as discussed
Comment 4 lars.langhans 2005-04-22 09:35:49 UTC
We will add the new jar entries with a simple basic procedure, which will run at
patch time.
Comment 5 lars.langhans 2005-04-22 11:27:48 UTC
fixed
Comment 6 svante.schubert 2005-05-31 16:28:40 UTC
Ready for QA

re-open issue and reassign to jsi@openoffice.org
Comment 7 svante.schubert 2005-05-31 16:28:49 UTC
reassign to jsi@openoffice.org
Comment 8 svante.schubert 2005-05-31 16:28:55 UTC
reset resolution to FIXED
Comment 9 jogi 2005-06-08 14:39:01 UTC
javarc now includes xalan.jar classpath as additional class.
Comment 10 jogi 2005-06-30 12:57:45 UTC
done