Thanks for your answer Benjamin I planned to support multiple testing scenarios. During development, developer can test directly on their own installation, but in the CI, it is nice to have everything deployed automatically.
I was not aware that the tomcat plugin could only deploy 1 war. This is good to know, as I spent some time today experimenting cargo. I used the zip installer, to get a tomcat 7.0.52 automatically. An so far this work very well. I have a bunch of integration test working. The only real issue I got was to provide external config file in the classpath of the webapp. I tried multiple combination to add an extra directory in the shared classpath of tomcat. In the end, I packaged the conf files in a jar and added the jar only in the shared classpath. Everything works and is elegant.
Gradle is so much pleasant to use than Maven And thanks for your plugins, cargo usage is great.
I was just wondering if the tomcat plugin would not have been better.