The automatic update system is fixed for Windows in Assemble 1.0.3 and S2S 2.0.2

If you're using Windows, you have probably observed that the update system is not working. The updating process is running well, but when you restart your graphical tool, it is not updated.

To update themselves, S2S and Assemble download the new files with the same name than the file to replace, but with a "_tmp" suffix. Once the new files fully downloaded, the "_tmp" version replaces the old one. Unfortunately, Windows is locking files when S2S or Assemble are running. So, it is not possible to replace files like assemble.jar, s2s.jar or paradise.jar. This is the situation i had under Windows 7 when i updated Assemble 1.0 to the recent 1.0.2 version:

You can see that i still have the new version as an assemble.jar_tmp file.

I fixed this bug in Assemble 1.0.3 and S2S 2.0.2. These versions are available today as automatic updates (Help Menu -> Update S2S/Assemble).

So, if you're using Windows, relaunch your update. This will make two modifications in your S2S/Assemble directory:
- a new file "updater.jar" appears
- the file launch_S2S/Assemble_for_Windows.bat has been improved. Don't forget to edit it with your favorite text editor to precise the location of your Java environment. 

Once S2S/Assemble restarted, you will get this window:

This indicates you that all the "_tmp" files have replaced the old ones:

Restart Assemble/S2S one more time. You should have the new version now. I have tested this bug fix under Windows 7 and Windows Vista. It should work for Windows XP. Just let me know...