Project setup

I know that's the way we invoke cucu in all our projects, but I find this method problematic and we work to change that.
The javaExec spawns another java process, so we have mem issues on jenkins in addition to zombies when aborting jobs. I believe the standard way of doing it is to make the cucu task a task of test type, and have a class (or more than one) that is a runner, annotated with Junit's @RunWith(Cucumber.class) this way tests are executed like a standard junit test.
Also it removes the dependency with the jar task, so it's cleaner.