Hello Thorsten,
Thorsten Ziehm wrote:
Hi Peter,
Peter Hillier-Brook wrote:
André Schnabel wrote:
Hi,
Peter Hillier-Brook schrieb:
I have to ask: why can't the installer interrogate the current
status of installed Java versions and choose NOT to install an
older version than presently available? It's not rocket
science, is it? :-)
Maybe - but it is not our task to solve this.
Sorry, I thought the installer was part of the project. If it is
not, then who is responsible for it so that they can be alerted to
the issue?
OOo installer trigger the Java installer. I think it is possible to
integrate a version identification in OOo installer. But in my
opinion it isn't the best to make the OOo installer more complex.
I fully understand that the root problem is the failure of the Java
installer to inspect its environment prior to installing a new (or
possibly older) version, but best practice suggests that if an OOo build
incorporates external packages such as Java, then surely it is incumbent
upon OOo to apply appropriate defensive coding in its own installer?
Just as an afterthought, suppose that the Java installer *did* check its
environment and refused to install an out of date version, what would
the effect of a generated failure condition be upon the OOo installer
(and hence the possibly naive user)?
Peter HB
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
