I found out today that the recently-released JRE 6u21 fixes one of our most-reported bugs, Byg 2552. Since this is a bug which affects file dialogs, it can prevent people (on Windows) from loading and saving files.
Due to the seriousness of this bug, I’m proposing that we set the Windows installer for the next release of VASSAL (3.1.15) to prompt the user to update Java if he has anything prior to 6u21 installed.
Thoughts? Objections?
I can’t think of a reason why we wouldn’t do this…
On 26 August 2010 16:06, uckelman uckelman@nomic.net wrote:
I found out today that the recently-released JRE 6u21 fixes one of our
most-reported bugs, Byg 2552[1]. Since this is a bug which affects file
dialogs, it can prevent people (on Windows) from loading and saving
files.Due to the seriousness of this bug, I’m proposing that we set the
Windows installer for the next release of VASSAL (3.1.15) to prompt the
user to update Java if he has anything prior to 6u21 installed.Thoughts? Objections?
I can’t think of a reason why we wouldn’t do this…
- M.
I found out today that the recently-released JRE 6u21 fixes one of our
most-reported bugs, Byg 2552[1]. Since this is a bug which affects file
dialogs, it can prevent people (on Windows) from loading and saving
files.
Due to the seriousness of this bug, I'm proposing that we set the
Windows installer for the next release of VASSAL (3.1.15) to prompt the
user to update Java if he has anything prior to 6u21 installed.
Thoughts? Objections?
[1] [vassalengine.org/tracker/sho ... gi?id=2552](http://www.vassalengine.org/tracker/show_bug.cgi?id=2552)