Couple of things that needed to be done.
One was to modify to the top-level pom so to avoid a known bug with Maven's antrun plugin where it uses the JRE instead of the JDK. This causes a problem on non-Mac systems when you want to compile (i.e. run javac) because it can't find the tools.jar. The bug is described here:
http://jira.codehaus.org/browse/MANTRUN-20
and a version of the workaround that I employed is found here:
http://docs.codehaus.org/display/MAVENUSER/Running+ant+tasks+that+use+the+JDK
Once Jenkins could run the Maven build from the top, we next needed to send the resulting snapshot artifacts to our own Maven repository. We currently us subversion to hold these files which is generally not recommended from what I read in many spots. In any case, I was eventually able to determine how to do it use a Google plugin that does pretty much what we want. So I created a new Jenkins job specifically to do a deploy. In addition to modifying the top-level pom file, I had to create a /home/builder/.m2/settings.xml file to hold the new credentials I created for the Jenkins build so that the job could check stuff into the repository. A test run made it all the way through and successfully checked the artifacts in.
New Feature
Major
MODIFY
/icepush/trunk/icepush/pom.xml
Couple of things that needed to be done.
One was to modify to the top-level pom so to avoid a known bug with Maven's antrun plugin where it uses the JRE instead of the JDK. This causes a problem on non-Mac systems when you want to compile (i.e. run javac) because it can't find the tools.jar. The bug is described here:
http://jira.codehaus.org/browse/MANTRUN-20
and a version of the workaround that I employed is found here:
http://docs.codehaus.org/display/MAVENUSER/Running+ant+tasks+that+use+the+JDK
Once Jenkins could run the Maven build from the top, we next needed to send the resulting snapshot artifacts to our own Maven repository. We currently us subversion to hold these files which is generally not recommended from what I read in many spots. In any case, I was eventually able to determine how to do it use a Google plugin that does pretty much what we want. So I created a new Jenkins job specifically to do a deploy. In addition to modifying the top-level pom file, I had to create a /home/builder/.m2/settings.xml file to hold the new credentials I created for the Jenkins build so that the job could check stuff into the repository. A test run made it all the way through and successfully checked the artifacts in.