Ummm... no.
Remember we don't run Windows and users don't really have the root password to their machines either ?
If we just dump it in our local repo, it can (or may not who knows) cause all kinds of side effects on stuff that actually *has* to work.
It's certainly on the to do list, but I wouldn't call a cluster wide upgrade "a few clicks".
Cheers,
Daniela
On 20 March 2013 15:19, John Kewley <
[log in to unmask] <mailto:
[log in to unmask]>> wrote:
L
The bugs meant that some users couldn’t run the tool at all and I
had heard there were some security issues with 1.6 so it is
probably a good plan to upgrade with 1.8 coming along this summer
as well.
Hopefully it is only a few key-clicks worth of inconvenience
Cheers
JK
<mailto:
[log in to unmask]>> wrote:
I thought you should know that we have recently released a new
version of CertWizard which has fixed some bugs.
The impact of this is that the Java libraries we were previously
using had known issues which they couldn’t fix
(for complicated backwards-compatible reasons) and therefore to
get the new interface which fixed them
we had to move to having minimum Java 1.7 on your systems
This means that those of you who only have Java 1.6 installed may
have issues when trying to run CW. The
solution is to upgrade to Java 1.7
Cheers and sorry for any inconvenience this may cause
JK
-- Scanned by iCritical.
-- Sent from the pit of despair
------------------------------
-----------------------------
