incubator-ooo-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 119525] AOo doesn't work with Java 1.7 on Windows
Date Tue, 18 Sep 2012 08:58:26 GMT

Ariel Constenla-Haile <> changed:

           What    |Removed                     |Added
           Keywords|needmoreinfo                |

--- Comment #40 from Ariel Constenla-Haile <> ---
(In reply to comment #39)
> Nice to hear that the issue was finally solved.
> I wonder why I had to go to Markmail to read the details.

This is just a bug report :)

> Besides the error shown by AOO was misleading and it was in part why it took
> so long to solve it.

Technical explanation (for the record):
The misleading part is AOO lists under Tools - Options - Java,  JREs that do
not work.

* it detects the JRE paths in the Windows registry
* it calls java.exe to get the properties
* if this call does not fail, and the Java virtual machine can be located, then
this JRE is added in the Options dialog

The problem is that while calling java.exe works, and the JVM library is there,
at the moment of using the JVM AOO tries to load the JVM library and it fails
to do so because of the missing VS C++ 2010 redist (Java 7 is built with VS C++
2010, but Oracle does not include the redis. in its installation).

An enhancement to make the User Experience better would be to only list in the
Options dialog does JRE where the JVM library can actually be loaded.

> A second wonder; could java be avoided in future versions of AOO?
> Or it is so deeply entangled on the suite's code it is just impossible...
> That is because just following Oracle's moves makes me wonder... nothing
> about java in specific but Oracle's doing...

It is possible, but someone has to do it; that is, write the code ;)
IMHO writing the Wizards in Java was a bad a design choice.
Also, the Online Help uses Apache Lucene in the background. There is a C++
implementation called CLucene, which has dual license (LGPL and ALv2).

You are receiving this mail because:
You are the assignee for the bug.

View raw message