Fix for not having a default newest-version minecraft_server jar url

[madeddie]

See issue: #168

There is no longer a default location for the newest minecraft_server.jar, instead the version can be found in a JSON file and the directory and file-naming structure is predictably using that version number.

[pjz]

If this goes in, can we get a version bump so 'msm update' will snag it?

[IronTetsubo]

re: getting a version bump, heh, unfortunately Marcus hasn't be updating/responding, so it's unlikely. Hopefully he pops back up from the dead and can take a look. I've pulled this patch into my repo (haven't quite committed it yet, still playing with things), and want to go a step further to add customer handlers in for the version files.

[IronTetsubo]

bump - zachlatta, strongly recommend this pull request or an equiv, as you can't use msm w/ 1.6 without it. this fixes issue #184, issue #169, and issue #168. Committing this + a version bump would make msm significantly more functional for everyone out of the box.

[dankegel]

Has teh fix been released yet? I just did a dumb fresh install, and ended up with a 1.5.2 server.
The workaround was to edit /opt/msm/jars/minecraft/target.txt to contain
https://s3.amazonaws.com/Minecraft.Download/versions/1.7.4/minecraft_server.1.7.4.jar
and run "msm jargroup getlatest minecraft".
(Or maybe "msm update", I dunno.)

[zachlatta]

Yeah, this has been merged, but not released yet. We're hoping to put together a release soon.

[air]

If like me you just want to know how to get MSM working, I wrote an article: http://www.aaronbell.com/how-to-run-minecraft-server-manager-on-amazon-linux/