Good idea, worked like a charm. Thanks for your help!
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-and-Jenkins-question-tp5738064p5738111.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---
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 you
could nest
I have a Git repository which is an application consisting of an EAR, WAR,
and JAR project. Each project has it's own pom.xml and then we have an
application level pom which just references the 3 modules. Our Jenkins job
will clone the git repository and use the high level pom to build the 3
arti
