MTE Updater First Release

[matshou]

This is a Java application compiled into an executable Jar using Gradle and it's Shadow plugin. It is intended to help users stay up to date with the new guide releases. Here is exactly how it works:

• The batch script "MTE-Updater.bat acts like a launcher that starts the main updater application (jar file) with the appropriate jvm arguments.
• The application then creates a copy of itself, launches it using windows cmd into a new java console window, then terminates itself.
• The copied or cloned application first checks if MWSE updater is present in the root directory and runs it. This way the user will update his MWSE build as well as the guide.
• It proceeds to download the remote version text file mte-version.txt located in the master repository branch and compares it's contents to that of the local version file provided in each release.
• If the commit SHA strings do not match, it means the local version of the guide in the root directory is out of date. This conclusion will also come if no version file is found in the root directory.
• Now that we need to update the application will ask the user if he wants to see the new changes to the guide. If the user says no, the application prints a note and terminates. If the user says yes, a Github webpage will be displayed in the new tab of the users default browser, containing a list of commits that were pushed since the last time the updater was ran. Along with this there is also a more detailed list of changes displayed in rich diff below the list of commits.
• Next the updater will copy all the files from the latest release (the release number is written as a first element inside the version file), extract them to a new directory, then copy and overwrite only those local files in root directory that need to be updated. We check for this using FileUtils.contentEqual method from the Apache Commons IO library.
• Lastly it will create an uninstaller batch script, write code inside it, run it using ProcessBuilder and terminate. The uninstaller script will run in the background and wait for the Java application to exit before it deletes it. It will then proceed to delete itself (batch scripts can do this).

Now we have all our files updated as well as a clean directory after the update is completed. I know this might be a bit of an over complicated solution to a simple problem of informing users that a markdown file has a new release, but this might serve as a framework for a more advanced application that manages your mod packages and ini tweaks later down the road.

I have supplied all updater files in this zip file: MTE-Release.zip.

Please extract them either to your MW root directory (preferably) or into a new empty directory and start the batch script. Give me your feedback and tell me what should change before it's properly released.

Thanks to @cpolera for helping setup the development environment and @DaelosTheCat for testing to make sure everything is in order. You guys have helped more then you think :smiley:

Note: Do not merge this pull request, only review it. The commits should be squashed into master but I am not sure if this will close the related issues that are referenced by the commits in this pull request. This is important for our future auto-built changelog implementation. Read the following referenced issue for more information:

Resolves #45

[Tyler799]

Excellent work, well done. Merged.

[matshou]

@Tyler799 You didn't read the whole thing:

Note: Do not merge this pull request, only review it. The commits should be squashed into master but I am not sure if this will close the related issues that are referenced by the commits in this pull request. This is important for our future auto-built changelog implementation. Read the following referenced issue for more information: