Issue 41673 - getSofficeNative does not support OOo
Summary: getSofficeNative does not support OOo
Status: CLOSED FIXED
Alias: None
Product: QA
Classification: Unclassified
Component: testscripts (show other issues)
Version: current
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: jogi
QA Contact: issues@qa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-31 06:53 UTC by jogi
Modified: 2013-08-07 15:06 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description jogi 2005-01-31 06:53:26 UTC 
Detected by Andre Schnabel:

In iniinfo.inc, Function getSofficeNative:
this Function is looking for OOo-Install path in registry under
\HKEY_LOCAL_MACHINE\Software\Sun Microsystems\%Productname%\%Version%

but the right path for OOo is
\HKEY_LOCAL_MACHINE\Software\OpenOffice.org\%Productname%\%Version%

After I Changed \Sun Microsystems\ to \OpenOffice.org\ all worked well.
Comment 1 joerg.skottke 2005-01-31 08:25:50 UTC 
Confirmed, this one blocks testing of CWS pyunofixes.
panic.
Comment 2 b.osi.ooo 2005-01-31 13:14:31 UTC 
started
Comment 3 b.osi.ooo 2005-01-31 13:35:05 UTC 
lowering priority;
Workaround is to use
http://qa.openoffice.org/qatesttool/index.html
"
To test OOo 1.9.x development builds you need to make a modification to the
TestTool settings.
...
"
Comment 4 b.osi.ooo 2005-01-31 15:14:32 UTC 
Checking in iniinfo.inc;
/cvs/qa/qatesttool/global/system/inc/iniinfo.inc,v  <--  iniinfo.inc
new revision: 1.37; previous revision: 1.36
done

Attention:
-------
On win32 systems development builds are not detected automatically!
Because the entry in the registry changes with every build (1.9.xy) and qaTestTool
has currently no chance 'to read tree entries, only values at the end of the path'
The entries will only added to ininfo.inc for Milestones (beta, final, update...)

For Development builds use the above mentioned 'TestTool settings'
Comment 5 b.osi.ooo 2005-01-31 15:14:53 UTC 
 reopen
Comment 6 b.osi.ooo 2005-01-31 15:15:17 UTC 
.
Comment 7 b.osi.ooo 2005-01-31 15:15:42 UTC 
 fixed
Comment 8 andreschnabel 2005-01-31 22:25:12 UTC 
verified.

Both works, the workaround as well, as detecting via Registry (if correct
version number is added).

I don't know why the workaround (OooProgramDir) didn't work yesterday. I could
not reproduce the problem (I got an timeout, weh Testtool was trying to start OOo)
Comment 9 jogi 2005-02-01 12:44:35 UTC 
closing