Continuous integration for Tantalum

Hi!

Part of the reason of originally moving the build over to Gradle was to enable us to have a repeatable build, and more importantly, CI for the project. JME has proved to be the tricky part, as none of the open providers seem to support JME/WTK-builds. The situation has not improved with the latest releases, which only run on Windows. We could trick the process to work (I've been able to build using Windows jars on my OS X) but I think we'd break several EULAs and would most probably get no support for setting this up.

In order to tackle the problem, we've talked with Paul to have the core library be built in standard Java, and only the platform specific builds require special frameworks and tools to build. This would also make the test setup a lot less intimidating, as we no longer need to have separate test projects to make it work. I've worked on this in the 'java_se_build'-branch, and finally got it working now. The results can be seen here: https://travis-ci.org/TantalumMobile/Tantalum/

Travis supports a lot of nice things, so it will e.g. build all new pull requests so that they can automatically be discarded would there be any problem with them. Travis also builds all the pushed branches, so there is no need for any extra config for that part.

The problem at the moment is that the only branch that actually supports CI-builds is the java_se-branch, as the other ones will fail due to missing Java ME-installation. My suggestion would be to verify that this branch works as expected also with the WTK-build, and then merge it in to master as soon as possible. Until we do so, most of the builds in Travis will be failed.

Please have a look, and let me know what you think. If we find it useful, I will write down some more details about this in the Wiki.

paulirotta / Tantalum

Continuous integration for Tantalum #47