Doh... just realized I didn't commit the correct relative path of the parent
pom in all the children ughh... I'll do that when I get home tonight,
don't want to commit to the project from work (pulled it down to demo it
today to the point haired folks)
I did look at using cargo underneath, but
You might want to look at Sonatype's m2eclipse-webby[1] for a very easy way to
startup web containers. It would probably be relatively straight forward to
integrate your code for runnings tests.
Webby leverages Cargo to start/stop containers and we've added debugging
support, resource filtering
On peripherally maven-dev related, but as thought leaders, I hope you guys
would take interest.
So I've been aggravated that I've had to start a web app up before running a
test in eclipse, given the way we typically run apps with things like the
jetty-maven-plugin (the startup/shutdown pre/post
