Build and upload Windows target with Travis CI

[dbaelz]

The build of the Windows target with the (experimental) Travis CI Windows image is stalled after the tests are executed. At the moment, this target is comment out in the Travis CI script. We should analyze why the build is stalled and fix it when possible. See this comment on #3 for details.

[DrewCarlson]

I managed to get Windows working with Travis for another project (see .travis.yml and a successful build).
Note that

• --no-daemon prevents build/deploy steps from stalling
• there is no caching because it is simply faster to download everything vs saving/loading cache archives; and
• The jdk home must be manually defined and the installed jdk version can change between builds (hence the dir step), I don't have a good solution for this yet.

[dbaelz]

I managed to get Windows working with Travis for another project (see .travis.yml and a successful build).
Sounds good. A working windows build and upload to travis ci would be great for the 1.0 release.

Note that

• --no-daemon prevents build/deploy steps from stalling
• there is no caching because it is simply faster to download everything vs saving/loading cache archives; and
• The jdk home must be manually defined and the installed jdk version can change between builds (hence the dir step), I don't have a good solution for this yet.
  The absolute JDK path and the installation is really ugly, but it's a first step. We could integrate it in Konclik in this way and check in the future for a better (then working) solution.

Would you recommend that we use this solution? If so, could you implement the changes and prepare a pull request?

[DrewCarlson]

The JDK home path is really the only issue since it will break builds when the Windows image is updated. I will open a PR when I find a better solution.