wrldwzrd89
Member
The problem is that you can't just dump DailyDownloader.jar in the same folder with the same name while it's still running. Windows won't allow it (but Unix platforms will). That's why ApplyUpdate exists. What's supposed to happen is that the old DailyDownloader grabs ApplyUpdate and the new version, launches ApplyUpdate and quits. ApplyUpdate then replaces DailyDownloader.jar with DailyDownloader-new.jar, and launches it, then itself quits. Furthermore, running ApplyUpdate manually is supposed to give an error, because it requires 2 arguments specified at the command line, which it needs to do its job properly.Here's what happens to me:
"Version 5.0.1 is out. You have Version 5.0.0"
I click ok.
Then I get release notes, and a download bar.
Then I click again, and the process repeats.
Further investigation shows that a file called DailyDownloader-new.jar was downloaded and did not replace the existing DailyDownloader.jar. Also it appears "ApplyUpdate-1.1.3.jar" was downloaded, which gives an error when run.
Is there any way that the auto-update could maybe replace DailyDownloader.jar with another file of the same name, that is updated, instead of dumping "DailyDownloader-new.jar" in my folder? This baffles my shortcuts.
As a manual work-around, delete the old DailyDownloader.jar, rename DailyDownloader-new.jar to DailyDownloader.jar and continue on, until I figure out what's going wrong.
Also, I've only tested this on OS X, where it works correctly. Could you please tell me which OS (Windows / Linux) and version / distribution you have? That would ease testing enormously.