[vassalengine-svn-trunk] [vassalengine-svn] SF.net SVN: vassalengine:[8774] VASSAL-src/trunk
Brought to you by:
rodneykinney,
uckelman
From: <uck...@us...> - 2013-06-23 15:16:05
|
Revision: 8774 http://sourceforge.net/p/vassalengine/svn/8774 Author: uckelman Date: 2013-06-23 15:16:00 +0000 (Sun, 23 Jun 2013) Log Message: ----------- Updated for 3.2.7 release. Modified Paths: -------------- VASSAL-src/trunk/CHANGES VASSAL-src/trunk/Makefile VASSAL-src/trunk/NOTES-bgg VASSAL-src/trunk/NOTES-csw VASSAL-src/trunk/NOTES-news VASSAL-src/trunk/NOTES-vassalforum VASSAL-src/trunk/README Modified: VASSAL-src/trunk/CHANGES =================================================================== --- VASSAL-src/trunk/CHANGES 2013-06-23 15:15:52 UTC (rev 8773) +++ VASSAL-src/trunk/CHANGES 2013-06-23 15:16:00 UTC (rev 8774) @@ -1,3 +1,23 @@ +3.2.7 - 23 June 2014 + +* 10261: Off-EDT UIManager.setLookAndFeel() causes lag on Apple Java +* 10256: StackOverflowError when Preferences can't be read +* 10249: Deck loses position over loading multiple player logs +* 10229: ArrayIndexOutOfBoundsException in RandomTextButton.DR +* 10217: Lose New Room selection field when changing from P2P to VASSAL server +* 10211: $oldLocation$ for Report Format is not set on Send To Location on + same map +* 10179: Module manager is overwriting P2P server preferences +* 10135: ClassCastException: GlobalProperties cannot be cast to Zone +* 10070: ClassCastException in DirectPeerPool.WTextArea() +* 9833: UnsatisfiedLinkError because JNA DLL cannot be read +* 9650: NPE in NodePlayer.toProperties() +* 3934: Windows installer launches VASSAL with admin privileges +* 3548: NumberFormatException in RandomTextButton.DR +* 2713: ClassCastException in P2PClient.playerToString() +* 2630: Editor crashes on close attempt when PieceDefiner is open +* 2545: NPE in TurnTracker$SetDialog.addChildControls() + 3.2.6 - 23 May 2013 * 10184: Test Mode Counter Refresh created duplicate counters Modified: VASSAL-src/trunk/Makefile =================================================================== --- VASSAL-src/trunk/Makefile 2013-06-23 15:15:52 UTC (rev 8773) +++ VASSAL-src/trunk/Makefile 2013-06-23 15:16:00 UTC (rev 8774) @@ -51,8 +51,8 @@ VNUM:=3.2.7 #SVNVERSION:=$(shell svnversion | perl -pe 's/(\d+:)?(\d+[MS]?)/$$2/; s/(\d+)M/$$1+1/e') SVNVERSION:=$(shell git svn log -1 --oneline | grep -oP '^r\K\d+') -VERSION:=$(VNUM)-svn$(SVNVERSION) -#VERSION:=$(VNUM) +#VERSION:=$(VNUM)-svn$(SVNVERSION) +VERSION:=$(VNUM) #CLASSPATH:=$(CLASSDIR):$(LIBDIR)/* Modified: VASSAL-src/trunk/NOTES-bgg =================================================================== --- VASSAL-src/trunk/NOTES-bgg 2013-06-23 15:15:52 UTC (rev 8773) +++ VASSAL-src/trunk/NOTES-bgg 2013-06-23 15:16:00 UTC (rev 8774) @@ -1,5 +1,5 @@ -[size=18][b]VASSAL 3.2.6 released[/b][/size] -The VASSAL Team is happy to announce the release of VASSAL 3.2.6, which fixes several problems found in earlier versions. +[size=18][b]VASSAL 3.2.7 released[/b][/size] +The VASSAL Team is happy to announce the release of VASSAL 3.2.7, which fixes several problems found in earlier versions. [size=16][b]IMPORTANT[/b][/size] * If you save a module, game, or log in VASSAL 3.2, you will NOT be able to open it afterwards with VASSAL 3.1. We recommend keeping a backup copy of any pre-3.2 files you plan to modify in 3.2 until you've verified that everything works to your satisfaction. @@ -10,14 +10,14 @@ * If some images display with incorrect colors, clear your tile cache (under Tools > Clear Tile Cache in the Module Manager) and reload the module. If the images still display with incorrect colors, PLEASE contact us indicating with which module you're seeing a problem. -* If you are using MacOS X 10.8.3 or later, you may see the message "VASSAL-3.2.6.app is damaged and can’t be opened. You should move it to the Trash." The problem is NOT that your download was corrupt, but rather that MacOS is preventing you from running VASSAL. To start VASSAL, control-click or right-click the app bundle's icon and select Open from the menu. You'll see a dialog asking whether you want to open VASSAL. Select "Open". Thereafter, you should be able to start VASSAL normally. +* If you are using MacOS X 10.8.3 or later, you may see the message "VASSAL-3.2.7.app is damaged and can’t be opened. You should move it to the Trash." The problem is NOT that your download was corrupt, but rather that MacOS is preventing you from running VASSAL. To start VASSAL, control-click or right-click the app bundle's icon and select Open from the menu. You'll see a dialog asking whether you want to open VASSAL. Select "Open". Thereafter, you should be able to start VASSAL normally. [size=16][b]Download[/b][/size] -[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-linux.tar.bz2]Linux[/url] -[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-macosx.dmg]Mac OS X[/url] -[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-windows.exe]Windows[/url] -[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-other.zip]Other[/url] -[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-src.zip]Source code[/url] +[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-linux.tar.bz2]Linux[/url] +[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-macosx.dmg]Mac OS X[/url] +[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-windows.exe]Windows[/url] +[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-other.zip]Other[/url] +[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-src.zip]Source code[/url] [size=16][b]Compatibility Notes[/b][/size] * VASSAL 3.2 is backwards compatible. VASSAL 3.1 is NOT forwards compatible. This means that modules, logs, and saves from VASSAL 3.1 should work in 3.2, but there is no guarantee that modules, logs, and saves from 3.2 will work in 3.1. Therefore, if you write a module, log, or save file in 3.2 DO NOT expect to be able to load it in 3.1. @@ -87,6 +87,25 @@ * Notify user when image loading fails [RFE 1887] +The following bugs in 3.2.6 are fixed in 3.2.7: + +* 10261: Off-EDT UIManager.setLookAndFeel() causes lag on Apple Java +* 10256: StackOverflowError when Preferences can't be read +* 10249: Deck loses position over loading multiple player logs +* 10229: ArrayIndexOutOfBoundsException in RandomTextButton.DR +* 10217: Lose New Room selection field when changing from P2P to VASSAL server +* 10211: $oldLocation$ for Report Format is not set on Send To Location on same map +* 10179: Module manager is overwriting P2P server preferences +* 10135: ClassCastException: GlobalProperties cannot be cast to Zone +* 10070: ClassCastException in DirectPeerPool.WTextArea() +* 9833: UnsatisfiedLinkError because JNA DLL cannot be read +* 9650: NPE in NodePlayer.toProperties() +* 3934: Windows installer launches VASSAL with admin privileges +* 3548: NumberFormatException in RandomTextButton.DR +* 2713: ClassCastException in P2PClient.playerToString() +* 2630: Editor crashes on close attempt when PieceDefiner is open +* 2545: NPE in TurnTracker$SetDialog.addChildControls() + The following bugs in 3.2.5 are fixed in 3.2.6: * 10184: Test Mode Counter Refresh created duplicate counters @@ -119,20 +138,10 @@ * 9694: NPE in ZipArchive.remove() * 9654: NPE in ZipArchive$ZipArchiveInputStream.close() -The following bugs in 3.2.3 are fixed in 3.2.4: +For changes prior to 3.2.5, see the change log. -* 10054: Add option to clear tile cache to Module Manager -* 10053: JPEGs with APP14 tags are incorrectly color-corrected by fix for Bug 9882 -* 10016: P2P Client/Server modes do not work in 3.2.2 -* 10012: NPE in EnumeratedPropertyPrompt.getNewValue() -* 9969: IllegalArgumentException in MapShader.PatternOp ctor -* 9823: No entry allowed for Peek command -* 9700: Unit activation improperly recorded +Please report all bugs in 3.2.7, even if they are bugs which you've already reported against other versions. We take your bug reports seriously---they're the reason we've been able to fix so many bugs. -For changes prior to 3.2.4, see the change log. - -Please report all bugs in 3.2.6, even if they are bugs which you've already reported against other versions. We take your bug reports seriously---they're the reason we've been able to fix so many bugs. - [size=16][b]Minimum Requirements[/b][/size] VASSAL 3.2 requires the Java Runtime Envrionment to run. @@ -140,7 +149,7 @@ MacOS X: The recommended minimum Java version for using VASSAL on MacOS X is 1.5.0_08 (a.k.a. Java 5 Update 8) for Macs where Java 6 is unavailable, and Java 6 or later for Macs where Java 6 is available. -Windows: The recommended minimum Java version for Windows is 1.6.0_21 (a.k.a. Java 6 Update 21). Windows users installing VASSAL with the Windows installer will be prompted to update Java if what they have is older than 1.6.0_35. After upgrading Java on Windows, you must restart your computer in order for Java programs to work properly. +Windows: The recommended minimum Java version for Windows is 1.6.0_45 (a.k.a. Java 6 Update 45). Windows users installing VASSAL with the Windows installer will be prompted to update Java if what they have is older than 1.6.0_45. After upgrading Java on Windows, you must restart your computer in order for Java programs to work properly. If you've installed Java 7 on Windows and thereafter VASSAL fails to launch: The Java 7 installer does not uninstall Java 6, and having both installed simultaneously prevents both from working properly. Therefore, check whether you also still have Java 6 installed. If so, removing Java 6 and rebooting will most likely solve your problem. Modified: VASSAL-src/trunk/NOTES-csw =================================================================== --- VASSAL-src/trunk/NOTES-csw 2013-06-23 15:15:52 UTC (rev 8773) +++ VASSAL-src/trunk/NOTES-csw 2013-06-23 15:16:00 UTC (rev 8774) @@ -1,4 +1,4 @@ -The VASSAL Team is happy to announce the release of VASSAL 3.2.6, which which fixes several problems found in earlier versions. +The VASSAL Team is happy to announce the release of VASSAL 3.2.7, which which fixes several problems found in earlier versions. <h3>IMPORTANT</h3> * If you save a module, game, or log in VASSAL 3.2, you will NOT be able to open it afterwards with VASSAL 3.1. We recommend keeping a backup copy of any pre-3.2 files you plan to modify in 3.2 until you've verified that everything works to your satisfaction. @@ -9,14 +9,14 @@ * If some images display with incorrect colors, clear your tile cache (under Tools > Clear Tile Cache in the Module Manager) and reload the module. If the images still display with incorrect colors, PLEASE contact us indicating with which module you're seeing a problem. -* If you are using MacOS X 10.8.3 or later, you may see the message "VASSAL-3.2.6.app is damaged and can’t be opened. You should move it to the Trash." The problem is NOT that your download was corrupt, but rather that MacOS is preventing you from running VASSAL. To start VASSAL, control-click or right-click the app bundle's icon and select Open from the menu. You'll see a dialog asking whether you want to open VASSAL. Select "Open". Thereafter, you should be able to start VASSAL normally. +* If you are using MacOS X 10.8.3 or later, you may see the message "VASSAL-3.2.7.app is damaged and can’t be opened. You should move it to the Trash." The problem is NOT that your download was corrupt, but rather that MacOS is preventing you from running VASSAL. To start VASSAL, control-click or right-click the app bundle's icon and select Open from the menu. You'll see a dialog asking whether you want to open VASSAL. Select "Open". Thereafter, you should be able to start VASSAL normally. <h3>Download</h3> -* <a href='http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-linux.tar.bz2' target='_new'>Linux</a> -* <a href='http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-macosx.dmg' target='_new'>Mac OS X</a> -* <a href='http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-windows.exe' target='_new'>Windows</a> -* <a href='http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-other.zip' target='_new'>Other</a> -* <a href='http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-src.zip' target='_new'>Source code</a> +* <a href='http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-linux.tar.bz2' target='_new'>Linux</a> +* <a href='http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-macosx.dmg' target='_new'>Mac OS X</a> +* <a href='http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-windows.exe' target='_new'>Windows</a> +* <a href='http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-other.zip' target='_new'>Other</a> +* <a href='http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-src.zip' target='_new'>Source code</a> <h3>Compatibility Notes</h3> * VASSAL 3.2 is backwards compatible. VASSAL 3.1 is NOT forwards compatible. This means that modules, logs, and saves from VASSAL 3.1 should work in 3.2, but there is no guarantee that modules, logs, and saves from 3.2 will work in 3.1. Therefore, if you write a module, log, or save file in 3.2 DO NOT expect to be able to load it in 3.1. @@ -87,6 +87,26 @@ * Notify user when image loading fails [RFE 1887] +The following bugs in 3.2.6 are fixed in 3.2.7: + +* 10261: Off-EDT UIManager.setLookAndFeel() causes lag on Apple Java +* 10256: StackOverflowError when Preferences can't be read +* 10249: Deck loses position over loading multiple player logs +* 10229: ArrayIndexOutOfBoundsException in RandomTextButton.DR +* 10217: Lose New Room selection field when changing from P2P to VASSAL server +* 10211: $oldLocation$ for Report Format is not set on Send To Location on + same map +* 10179: Module manager is overwriting P2P server preferences +* 10135: ClassCastException: GlobalProperties cannot be cast to Zone +* 10070: ClassCastException in DirectPeerPool.WTextArea() +* 9833: UnsatisfiedLinkError because JNA DLL cannot be read +* 9650: NPE in NodePlayer.toProperties() +* 3934: Windows installer launches VASSAL with admin privileges +* 3548: NumberFormatException in RandomTextButton.DR +* 2713: ClassCastException in P2PClient.playerToString() +* 2630: Editor crashes on close attempt when PieceDefiner is open +* 2545: NPE in TurnTracker$SetDialog.addChildControls() + The following bugs in 3.2.5 are fixed in 3.2.6: * 10184: Test Mode Counter Refresh created duplicate counters @@ -119,20 +139,10 @@ * 9694: NPE in ZipArchive.remove() * 9654: NPE in ZipArchive$ZipArchiveInputStream.close() -The following bugs in 3.2.3 are fixed in 3.2.4: +For changes prior to 3.2.5, see the change log. -* 10054: Add option to clear tile cache to Module Manager -* 10053: JPEGs with APP14 tags are incorrectly color-corrected by fix for Bug 9882 -* 10016: P2P Client/Server modes do not work in 3.2.2 -* 10012: NPE in EnumeratedPropertyPrompt.getNewValue() -* 9969: IllegalArgumentException in MapShader.PatternOp ctor -* 9823: No entry allowed for Peek command -* 9700: Unit activation improperly recorded +Please report all bugs in 3.2.7, even if they are bugs which you've already reported against other versions. We take your bug reports seriously---they're the reason we've been able to fix so many bugs. -For changes prior to 3.2.4, see the change log. - -Please report all bugs in 3.2.6, even if they are bugs which you've already reported against other versions. We take your bug reports seriously---they're the reason we've been able to fix so many bugs. - <h3>Minimum Requirements</h3> VASSAL 3.2 requires the Java Runtime Envrionment to run. @@ -140,7 +150,7 @@ MacOS X: The recommended minimum Java version for using VASSAL on MacOS X is 1.5.0_08 (a.k.a. Java 5 Update 8 ) for Macs where Java 6 is unavailable, and Java 6 or later for Macs where Java 6 is available. -Windows: The recommended minimum Java version for Windows is 1.6.0_21 (a.k.a. Java 6 Update 21). Windows users installing VASSAL with the Windows installer will be prompted to update Java if what they have is older than 1.6.0_35. After upgrading Java on Windows, you must restart your computer in order for Java programs to work properly. +Windows: The recommended minimum Java version for Windows is 1.6.0_45 (a.k.a. Java 6 Update 45). Windows users installing VASSAL with the Windows installer will be prompted to update Java if what they have is older than 1.6.0_45. After upgrading Java on Windows, you must restart your computer in order for Java programs to work properly. If you've installed Java 7 on Windows and thereafter VASSAL fails to launch: The Java 7 installer does not uninstall Java 6, and having both installed simultaneously prevents both from working properly. Therefore, check whether you also still have Java 6 installed. If so, removing Java 6 and rebooting will most likely solve your problem. Modified: VASSAL-src/trunk/NOTES-news =================================================================== --- VASSAL-src/trunk/NOTES-news 2013-06-23 15:15:52 UTC (rev 8773) +++ VASSAL-src/trunk/NOTES-news 2013-06-23 15:16:00 UTC (rev 8774) @@ -1,5 +1,5 @@ <p> -The VASSAL Team is happy to announce the release of VASSAL 3.2.6, which which fixes several problems found in earlier versions. +The VASSAL Team is happy to announce the release of VASSAL 3.2.7, which which fixes several problems found in earlier versions. </p> <h2>IMPORTANT</h2> @@ -8,16 +8,16 @@ <li>If you found it necessary to set a very large maximum heap (> 512MB) for a module with VASSAL 3.1, it should now be possible with VASSAL 3.2 to set a much lower maximum heap and achieve similar or better display performance. 512MB should now be adequate for most modules.</li> <li>VASL 5.9.3 and earlier are not compatible with VASSAL 3.2. Work to update VASL for 3.2 is nearly finished.</li> <li>If some images display with incorrect colors, clear your tile cache (under Tools > Clear Tile Cache in the Module Manager) and reload the module. If the images still display with incorrect colors, PLEASE contact us indicating with which module you're seeing a problem.</li> - <li>If you are using MacOS X 10.8.3 or later, you may see the message "VASSAL-3.2.6.app is damaged and can’t be opened. You should move it to the Trash." The problem is NOT that your download was corrupt, but rather that MacOS is preventing you from running VASSAL. To start VASSAL, control-click or right-click the app bundle's icon and select Open from the menu. You'll see a dialog asking whether you want to open VASSAL. Select "Open". Thereafter, you should be able to start VASSAL normally.</li> + <li>If you are using MacOS X 10.8.3 or later, you may see the message "VASSAL-3.2.7.app is damaged and can’t be opened. You should move it to the Trash." The problem is NOT that your download was corrupt, but rather that MacOS is preventing you from running VASSAL. To start VASSAL, control-click or right-click the app bundle's icon and select Open from the menu. You'll see a dialog asking whether you want to open VASSAL. Select "Open". Thereafter, you should be able to start VASSAL normally.</li> </ul> <h2>Download</h2> <ul> - <li><a href="http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-linux.tar.bz2" target="_blank">Linux</a></li> - <li><a href="http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-macosx.dmg">Mac OS X</a></li> - <li><a href="http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-windows.exe">Windows</a></li> - <li><a href="http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-other.zip">Other</a></li> - <li><a href="http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-src.zip">Source</a></li> + <li><a href="http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-linux.tar.bz2" target="_blank">Linux</a></li> + <li><a href="http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-macosx.dmg">Mac OS X</a></li> + <li><a href="http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-windows.exe">Windows</a></li> + <li><a href="http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-other.zip">Other</a></li> + <li><a href="http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-src.zip">Source</a></li> </ul> <h2>Compatibility Notes</h2> <ul> @@ -90,6 +90,27 @@ <li>Notify user when image loading fails [RFE 1887]</li> </ul> <p> +The following bugs in 3.2.6 are fixed in 3.2.7: +<ul> + <li>10261: Off-EDT UIManager.setLookAndFeel() causes lag on Apple Java</li> + <li>10256: StackOverflowError when Preferences can't be read</li> + <li>10249: Deck loses position over loading multiple player logs</li> + <li>10229: ArrayIndexOutOfBoundsException in RandomTextButton.DR</li> + <li>10217: Lose New Room selection field when changing from P2P to VASSAL server</li> + <li>10211: $oldLocation$ for Report Format is not set on Send To Location on same map</li> + <li>10179: Module manager is overwriting P2P server preferences</li> + <li>10135: ClassCastException: GlobalProperties cannot be cast to Zone</li> + <li>10070: ClassCastException in DirectPeerPool.WTextArea()</li> + <li>9833: UnsatisfiedLinkError because JNA DLL cannot be read</li> + <li>9650: NPE in NodePlayer.toProperties()</li> + <li>3934: Windows installer launches VASSAL with admin privileges</li> + <li>3548: NumberFormatException in RandomTextButton.DR</li> + <li>2713: ClassCastException in P2PClient.playerToString()</li> + <li>2630: Editor crashes on close attempt when PieceDefiner is open</li> + <li>2545: NPE in TurnTracker$SetDialog.addChildControls()</li> +</ul> +</p> +<p> The following bugs in 3.2.5 are fixed in 3.2.6: <ul> <li>10184: Test Mode Counter Refresh created duplicate counters</li> @@ -126,23 +147,11 @@ </ul> </p> <p> -The following bugs in 3.2.3 are fixed in 3.2.4: -<ul> - <li>10054: Add option to clear tile cache to Module Manager</li> - <li>10053: JPEGs with APP14 tags are incorrectly color-corrected by fix for Bug 9882</li> - <li>10016: P2P Client/Server modes do not work in 3.2.2</li> - <li>10012: NPE in EnumeratedPropertyPrompt.getNewValue()</li> - <li>9969: IllegalArgumentException in MapShader.PatternOp ctor</li> - <li>9823: No entry allowed for Peek command</li> - <li>9700: Unit activation improperly recorded</li> -</ul> +For changes prior to 3.2.5, see the change log. </p> <p> -For changes prior to 3.2.4, see the change log. +Please report all bugs in 3.2.7 even if they are bugs which you've already reported against other versions. We take your bug reports seriously—they're the reason we've been able to fix so many bugs. </p> -<p> -Please report all bugs in 3.2.6 even if they are bugs which you've already reported against other versions. We take your bug reports seriously—they're the reason we've been able to fix so many bugs. -</p> <h2>Minimum Requirements</h2> <p> @@ -155,7 +164,7 @@ MacOS X: The recommended minimum Java version for using VASSAL on MacOS X is 1.5.0_08 (a.k.a. Java 5 Update 8) for Macs where Java 6 is unavailable, and Java 6 or later for Macs where Java 6 is available. </p> <p> -Windows: The recommended minimum Java version for Windows is 1.6.0_21 (a.k.a. Java 6 Update 21). Windows users installing VASSAL with the Windows installer will be prompted to update Java if what they have is older than 1.6.0_35. After upgrading Java on Windows, you must restart your computer in order for Java programs to work properly. +Windows: The recommended minimum Java version for Windows is 1.6.0_45 (a.k.a. Java 6 Update 45). Windows users installing VASSAL with the Windows installer will be prompted to update Java if what they have is older than 1.6.0_45. After upgrading Java on Windows, you must restart your computer in order for Java programs to work properly. </p> <p> If you've installed Java 7 on Windows and thereafter VASSAL fails to launch: The Java 7 installer does not uninstall Java 6, and having both installed simultaneously prevents both from working properly. Therefore, check whether you also still have Java 6 installed. If so, removing Java 6 and rebooting will most likely solve your problem. Modified: VASSAL-src/trunk/NOTES-vassalforum =================================================================== --- VASSAL-src/trunk/NOTES-vassalforum 2013-06-23 15:15:52 UTC (rev 8773) +++ VASSAL-src/trunk/NOTES-vassalforum 2013-06-23 15:16:00 UTC (rev 8774) @@ -1,6 +1,6 @@ -[size=200][b]VASSAL 3.2.6 released[/b][/size] +[size=200][b]VASSAL 3.2.7 released[/b][/size] -The VASSAL Team is happy to announce the release of VASSAL 3.2.6, which which fixes several problems found in earlier versions. +The VASSAL Team is happy to announce the release of VASSAL 3.2.7, which which fixes several problems found in earlier versions. [size=150][b]IMPORTANT[/b][/size] @@ -11,15 +11,15 @@ * VASL 5.9.3 and earlier are not compatible with VASSAL 3.2. Work to update VASL for 3.2 is nearly finished. -* If you are using MacOS X 10.8.3 or later, you may see the message "VASSAL-3.2.6.app is damaged and can’t be opened. You should move it to the Trash." The problem is NOT that your download was corrupt, but rather that MacOS is preventing you from running VASSAL. To start VASSAL, control-click or right-click the app bundle's icon and select Open from the menu. You'll see a dialog asking whether you want to open VASSAL. Select "Open". Thereafter, you should be able to start VASSAL normally. +* If you are using MacOS X 10.8.3 or later, you may see the message "VASSAL-3.2.7.app is damaged and can’t be opened. You should move it to the Trash." The problem is NOT that your download was corrupt, but rather that MacOS is preventing you from running VASSAL. To start VASSAL, control-click or right-click the app bundle's icon and select Open from the menu. You'll see a dialog asking whether you want to open VASSAL. Select "Open". Thereafter, you should be able to start VASSAL normally. [size=150][b]Download[/b][/size] -[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-linux.tar.bz2]Linux[/url] -[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-macosx.dmg]Mac OS X[/url] -[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-windows.exe]Windows[/url] -[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-other.zip]Other[/url] -[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-src.zip]Source code[/url] +[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-linux.tar.bz2]Linux[/url] +[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-macosx.dmg]Mac OS X[/url] +[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-windows.exe]Windows[/url] +[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-other.zip]Other[/url] +[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-src.zip]Source code[/url] [size=150][b]Compatibility Notes[/b][/size] @@ -96,6 +96,25 @@ * Notify user when image loading fails [RFE 1887] +The following bugs in 3.2.6 are fixed in 3.2.7: + +* 10261: Off-EDT UIManager.setLookAndFeel() causes lag on Apple Java +* 10256: StackOverflowError when Preferences can't be read +* 10249: Deck loses position over loading multiple player logs +* 10229: ArrayIndexOutOfBoundsException in RandomTextButton.DR +* 10217: Lose New Room selection field when changing from P2P to VASSAL server +* 10211: $oldLocation$ for Report Format is not set on Send To Location on same map +* 10179: Module manager is overwriting P2P server preferences +* 10135: ClassCastException: GlobalProperties cannot be cast to Zone +* 10070: ClassCastException in DirectPeerPool.WTextArea() +* 9833: UnsatisfiedLinkError because JNA DLL cannot be read +* 9650: NPE in NodePlayer.toProperties() +* 3934: Windows installer launches VASSAL with admin privileges +* 3548: NumberFormatException in RandomTextButton.DR +* 2713: ClassCastException in P2PClient.playerToString() +* 2630: Editor crashes on close attempt when PieceDefiner is open +* 2545: NPE in TurnTracker$SetDialog.addChildControls() + The following bugs in 3.2.5 are fixed in 3.2.6: * 10184: Test Mode Counter Refresh created duplicate counters @@ -128,20 +147,10 @@ * 9694: NPE in ZipArchive.remove() * 9654: NPE in ZipArchive$ZipArchiveInputStream.close() -The following bugs in 3.2.3 are fixed in 3.2.4: +For changes prior to 3.2.5, see the change log. -* 10054: Add option to clear tile cache to Module Manager -* 10053: JPEGs with APP14 tags are incorrectly color-corrected by fix for Bug 9882 -* 10016: P2P Client/Server modes do not work in 3.2.2 -* 10012: NPE in EnumeratedPropertyPrompt.getNewValue() -* 9969: IllegalArgumentException in MapShader.PatternOp ctor -* 9823: No entry allowed for Peek command -* 9700: Unit activation improperly recorded +Please report all bugs in 3.2.7, even if they are bugs which you've already reported against other versions. We take your bug reports seriously---they're the reason we've been able to fix so many bugs. -For changes prior to 3.2.4, see the change log. - -Please report all bugs in 3.2.6, even if they are bugs which you've already reported against other versions. We take your bug reports seriously---they're the reason we've been able to fix so many bugs. - [size=150][b]Minimum Requirements[/b][/size] VASSAL 3.2 requires the Java Runtime Envrionment to run. @@ -150,7 +159,7 @@ MacOS X: The recommended minimum Java version for using VASSAL on MacOS X is 1.5.0_08 (a.k.a. Java 5 Update 8) for Macs where Java 6 is unavailable, and Java 6 or later for Macs where Java 6 is available. -Windows: The recommended minimum Java version for Windows is 1.6.0_21 (a.k.a. Java 6 Update 21). Windows users installing VASSAL with the Windows installer will be prompted to update Java if what they have is older than 1.6.0_35. After upgrading Java on Windows, you must restart your computer in order for Java programs to work properly. +Windows: The recommended minimum Java version for Windows is 1.6.0_45 (a.k.a. Java 6 Update 45). Windows users installing VASSAL with the Windows installer will be prompted to update Java if what they have is older than 1.6.0_45. After upgrading Java on Windows, you must restart your computer in order for Java programs to work properly. If you've installed Java 7 on Windows and thereafter VASSAL fails to launch: The Java 7 installer does not uninstall Java 6, and having both installed simultaneously prevents both from working properly. Therefore, check whether you also still have Java 6 installed. If so, removing Java 6 and rebooting will most likely solve your problem. Modified: VASSAL-src/trunk/README =================================================================== --- VASSAL-src/trunk/README 2013-06-23 15:15:52 UTC (rev 8773) +++ VASSAL-src/trunk/README 2013-06-23 15:16:00 UTC (rev 8774) @@ -1,4 +1,4 @@ -The VASSAL Team is happy to announce the release of VASSAL 3.2.6, which +The VASSAL Team is happy to announce the release of VASSAL 3.2.7, which which fixes several problems found in earlier versions. ******************************************************************************** @@ -24,7 +24,7 @@ indicating with which module you're seeing a problem. * If you are using MacOS X 10.8.3 or later, you may see the message - "VASSAL-3.2.6.app is damaged and can’t be opened. You should move it to + "VASSAL-3.2.7.app is damaged and can’t be opened. You should move it to the Trash." The problem is NOT that your download was corrupt, but rather that MacOS is preventing you from running VASSAL. To start VASSAL, control- click or right-click the app bundle's icon and select Open from the menu. @@ -42,23 +42,23 @@ For Linux: - http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-linux.tar.bz2 + http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-linux.tar.bz2 For Mac OS X: - http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-macosx.dmg + http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-macosx.dmg For Windows: - http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-windows.exe + http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-windows.exe For other operating systems: - http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-other.zip + http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-other.zip Source code: - http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.6-src.zip + http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.7-src.zip ********************* Compatibility Notes @@ -233,20 +233,9 @@ * 9694: NPE in ZipArchive.remove() * 9654: NPE in ZipArchive$ZipArchiveInputStream.close() -The following bugs in 3.2.3 are fixed in 3.2.4: +For changes prior to 3.2.5, see the change log. -* 10054: Add option to clear tile cache to Module Manager -* 10053: JPEGs with APP14 tags are incorrectly color-corrected by fix for - Bug 9882 -* 10016: P2P Client/Server modes do not work in 3.2.2 -* 10012: NPE in EnumeratedPropertyPrompt.getNewValue() -* 9969: IllegalArgumentException in MapShader.PatternOp ctor -* 9823: No entry allowed for Peek command -* 9700: Unit activation improperly recorded - -For changes prior to 3.2.4, see the change log. - -Please report all bugs in 3.2.6 even if they are bugs which you've already +Please report all bugs in 3.2.7 even if they are bugs which you've already reported against other versions. We take your bug reports seriously---they're the reason we've been able to fix so many bugs. This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ vassalengine-svn mailing list vas...@li... https://lists.sourceforge.net/lists/listinfo/vassalengine-svn |