mkovatsc/Californium — pull request #8 by brice-morin (2012-04-27 14:03:42+00:00)
Title: Support for continuous integration in Californium

Hi,

My fork is based on your latest version of Cf. It provides support for Maven and for continuous integration. Everytime time a commit is made on Cf (well, on my fork) it triggers a build and automatically runs all the tests on our Jenkins server (http://build.thingml.org/). We can for example see that a few tests fail (http://build.thingml.org/job/Build%20Californium/)

Looking at:
http://build.thingml.org/job/Build%20Californium/ch.ethz.inf.vs$ch.ethz.inf.vs.californium/15/testReport/

we can see that:
- 2 are in error because of a null pointer exception
- 2 test fail (because of an assert)
- 1 test fails because of a timeout (basically it seemed to freeze and I added a timeout)

Also when a build succeed, the latest version of the jar are provisionned on our server (publicly available), so that users of Cf can get the latest version of Cf with no need to compile them manually from the sources.

I think the support for Maven and the continuous integration provides an added value. Please note that it is still possible to use Cf without Maven (eg in Eclipse without the Maven plugin), so there is no overhead for developpers not willing to use Maven.

Maybe you could try my fork and eventually integrate it?

Thanks,

Brice.