To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=115180
------- Additional comments from [email protected] Tue Oct 26 18:55:53 +0000 2010 ------- @chcd: Agreed, concerning the problems and can of worms with reverting to an older Java installation. >and then OO.org, which didn't receive notifications >until the end users notice the problems. Maybe because they have slept and have been uninformed? And didn't seem to read and follow neither the Developer Release Notes Apple has regulary enclosed with its Java Previews in its free (!) ADC Download area since over a year nor the since month public available statements of Mike Swingler, Java Runtime Engineer, Apple Inc.? The OOo team/Sun/Oracle may have known since month all about this and all about this potential risk and potential trouble -- at least since February 2010 -- and could have changed its Java detection code early enough to what Apple recommends since over a year. Please read my comments and links to this bug, especially my two links from Oct 24 23:38:50 to Apples java-dev Mailinglist entries from February 2010: http://lists.apple.com/archives/java-dev/2010/Feb/msg00132.html http://lists.apple.com/archives/java-dev/2010/Feb/msg00150.html Curious, that NeoOffice is NOT in trouble caused by this recent Java update, because the NeoOffice team has obviously changed and adapted its JRE detection code early enough (many month or years ago). This is, what they say to this whole mess: http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&p=60996#60996 I think, this issue, this mess, could have been totally avoidable. And it's not Apple to blame on this in the first place but OpenOffice/Sun/Oracle. It's very awkward and puts a bad light onto OpenOffice/Oracle (QA?), and it is grist to the mills of forks like LibreOffice and NeoOffice and gives the user/Mac user once more a reason to prefer or switch over to LibreOffice/NeoOffice. Or they flee into the arms of Microsoft and use their MS Office. Please, such kinds of issues like this should never happen again. Because this particulary issue has been so foreseeable, avoidable and finally is so dispensable. This issue should be a warning sign to improve QA and to better hear and look what's going on on the platforms -- especially relating the Mac platform (including better platform integration and adherence/impementation of the platform-specific Human Interface Guidelines). Where are the observable results of Oracle's promises to more foster Sun's heritage with more developers and more money? Changing just icons ist not enough. --------------------------------------------------------------------- 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]
