While using the above beta I found a function could not run because it requires Java. I'm almost certain the function worked in Beta 1.
I checked Preferences to find that no Java runtime was registered despite having the lastest Mac release of it (as of today). Attempts to load and register Java within LO Preferences failed despite indications that it attempts to register.
NeoOffice has the latest Java Runtime correctly registered and functions appropriately.
Further to my initial comment. I have since test installed OO 3.3 RC and, what appears to be the same JAVA issue, occurs with it.
I have changed the platform in this issue to Mac since it only affects that OS.
This bug is already known for the current OOo and future 3.3 betas :
It is due apparently to Apple's wondrous update of Java to version 1.6.0_22 and OOo's non-standard way of looking for the presence of the JVM and determining its version number.
Not only does this screw up the betas, but it also screws up any existing version that is installed or re-installed (apparently, and judging from the very irate comments on the OOo user groups).
I wonder if the Java detection code from NeoOffice can be used in LO to detect Apple's Java 1.6.0_22 "wondrous" update. NeoOffice seems to detect the Java location correctly.
In addition, when disabling Java support in the options, nearly every action (like copy and paste, or printing) throws an "This function needs Java" error message, although I'm pretty sure these functions do not require Java at all.
m13 was merged today, it should fix this.
*** Bug 31260 has been marked as a duplicate of this bug. ***
Fixed indeed. we should have a beta update soon.
(In reply to comment #8)
> Fixed indeed. we should have a beta update soon.
Closing - Sophie