I thought about the shell script idea as well, but would prefer just a single step of pointing it to the parent pom and everything is handled. Leaving the configuration out of Jenkins and putting it into the POM. Something along the lines of in the parent POM where you specify the <modules> you could nest <goals> per module. I know that probably doesn't exist but thats the kind of functionality i'm looking for.
-- View this message in context: http://maven.40175.n5.nabble.com/Maven-and-Jenkins-question-tp5738064p5738077.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
