| Summary: | : LO should use a private java runtime, not a system wide one. | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | tortino <tortino> |
| Component: | Installation | Assignee: | Andras Timar <timar74> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | 3.6.0.4 release | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | BSA | ||
| Crash report or crash signature: | Regression By: | ||
|
Description
tortino
2012-08-31 09:22:10 UTC
I have a better proposal: to remove Java from LO completely. That festering unmaintainable security hole has no place on user machines. (In reply to comment #1) > I have a better proposal: to remove Java from LO completely. That festering > unmaintainable security hole has no place on user machines. well, I agree to remove java, but there is a lot of code to be converted, it won't happen soon (if at all). try searching for "java" in bugzilla, it seems no easy to remove it (mainly because of base and hsqldb). so the private jre can help fixing many problems in a short time. We do not want to bundle JRE into LibreOffice Windows installer. 1) size 2) uncertainty around the license well, about size I cannot comment, hovever license is permitted by oracle, and there is also a list of files in the jdk that you can remove, if you don't need it. see here: http://www.oracle.com/technetwork/java/javase/terms/readme/index.html As an example for JRE 7: To run your application, a user needs the Java SE Runtime Environment, which is freely available from Oracle. Or, you can redistribute the Java SE Runtime Environment for free with your application, according to the terms of the Oracle Binary Code License Agreement for the Java SE Platform Products. <...cut...> The files that make up the Java SE Runtime Environment are divided into two categories: required and optional. Optional files may be excluded from redistributions of the Java SE Runtime Environment at the vendor's discretion. so the license is not a problem. the only problem is size, but this feature can resolve quite some problems of compatibility with users' systems (and don't forget ease of use: just install LO, don't bother woth Java). So maybe it's worth reevaluating. Thanks. |