On 4/21/2018 10:00 AM, Peter Kovacs wrote:
> As I pointed out that we move the core java functionality to be Java 9
> compatible.
> Also a 64 bit Windows migration is on the way.
> Plus we move to MSVC 2015. Should therefore close the gaps you have in mind
> for 4.2.0.
>
> I don't think that jav
On 04/21/2018 10:40 AM, Matthias Seidel wrote:
> Hi Kay,
>
> Am 21.04.2018 um 19:25 schrieb Kay Schenk:
>> The latest output build I installed --
>> rpm_en-US_2018-04-15_22_15_10_1829228
>
> Assuming you downloaded from buildbot, can you try:
> https://ci.apache.org/projects/openoffice/install/
Hi Kay,
Am 21.04.2018 um 19:25 schrieb Kay Schenk:
> The latest output build I installed --
> rpm_en-US_2018-04-15_22_15_10_1829228
Assuming you downloaded from buildbot, can you try:
https://ci.apache.org/projects/openoffice/install/linux32/Apache_OpenOffice_4.2.0_Linux_x86_install-rpm_en-US_201
The latest output build I installed --
rpm_en-US_2018-04-15_22_15_10_1829228
on my 32-bit CentOS 6.9 is non-functioning. Errors attached.
--
--
MzK
"Less is MORE."
--
On Sat, Apr 21, 2018, 6:36 AM Pedro Lino wrote:
>
> People reading something, jumping to conclusions, and freaking out. Move
> along, nothing to see here...
>
>
> I don't think so. Maybe there is a good reason why another office suite
> moved all the scripting to Python.
>
I don't want a broken
As I pointed out that we move the core java functionality to be Java 9
compatible.
Also a 64 bit Windows migration is on the way.
Plus we move to MSVC 2015. Should therefore close the gaps you have in mind for
4.2.0.
I don't think that java license for cooperation is an issue.
Am 21. April 20
> People reading something, jumping to conclusions, and freaking out. Move
> along, nothing to see here...
>
I don't think so. Maybe there is a good reason why another office suite moved
all the scripting to Python.
> Facts: there are OpenJDK builds for Windows, Linux, Mac and even Linux