Bug 65179 - CONFIGURATION: Java is now under Advanced - Errors still reference Java
Summary: CONFIGURATION: Java is now under Advanced - Errors still reference Java
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version: 4.0.3.3 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard: BSA
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-05-30 14:49 UTC by crazyskeggy
Modified: 2013-05-30 15:54 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description crazyskeggy 2013-05-30 14:49:27 UTC
Problem description: 

Somebody on Ask LibO saw the following message: "The LibreOffice configuration has been changed. Under Tools - Options - LibreOffice - Java, select the Java runtime environment you want to have used by LibreOffice." but in Tools > Options > LibreOffice > Java doesn't exist. Instead those settings are now in Tools > Options > LibreOffice > Advanced.

(Ref: http://ask.libreoffice.org/en/question/18251/i-get-the-following-message-the-libreoffice/)

Steps to reproduce:
1. Open Tools > Options / LibreOffice > Preferences
2. Expand the LibreOffice section on the left.
3. Find the Java settings.

Current behavior:
The location of Java settings are under Advanced, whilst the error says they are under Java.

Expected behavior:
The error message and Options dialog match.
              
Operating System: Windows XP
Version: 4.0.3.3 release
Comment 1 Jorendc 2013-05-30 15:18:07 UTC
Hi,

Thanks for reporting.

This is fixed already (see http://opengrok.libreoffice.org/xref/core/svtools/source/java/javaerror.src#29 and commit http://cgit.freedesktop.org/libreoffice/core/commit/?id=33a87b9339e26290f5a3c000bc5951af44e9ccf1), but I think it isn't backported to LibreOffice-4-0 due the string freeze.

Although this, it is fixed, and is correct in LibreOffice-4-1.

@Timar: Am I right?

Kind regards,
Joren
Comment 2 crazyskeggy 2013-05-30 15:54:39 UTC
Could this not even be included in 4.0.4 as a bugfix? I don't know what the dev policies on this are, so...

Also, what time is 4.1 due out? That way I can let the user know that this has been fixed.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.