Thanks for your reply. I corrected the documentation regarding this as otherwise users would think we would really fork a new JVM process like the way you can do today for example using the Maven Surefire Plugin's forkMode etc.
Babak Claus Ibsen-2 wrote > Hi > > Yeah it runs in the same JVM. > Its no different than for example if you > > cd examples > cd camel-example-servlet-tomcat > mvn jetty:run > > And startup an embedded jetty server for this WAR project > > And if you want to use tomcat instead you can type > mvn tomcat7:run > > > > On Mon, Dec 2, 2013 at 1:35 PM, Babak Vahdat > < > babak.vahdat@ > > wrote: >> Hi >> >> The Camel Maven Plugin is a hot topic these days :) so I came accross >> something which I think the documentation is wrong: >> >> http://camel.apache.org/camel-maven-plugin.html >> >> As I was looking into my own comment for CAMEL-7028 I realized that our >> RunMojo boots up Camel JUST inside a new Thread of the SAME process Maven >> already running inside. But does not really spawn a NEW JVM at all. I'm >> NOT a Maven expert so please correct me if I'm wrong. >> >> Babak >> >> > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: > cibsen@ > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen -- View this message in context: http://camel.465427.n5.nabble.com/Does-the-run-goal-of-the-Camel-Maven-Plugin-really-boots-up-a-new-JVM-tp5744183p5744187.html Sent from the Camel Development mailing list archive at Nabble.com.
