Hello Option a) is probably something we can solve with an extension mechanism in maven3. If you have time to load an issue ?. Btw some ci server handles this case.
-- Olivier Le 17 oct. 2011 01:22, "Michael L. Hartery" <[email protected]> a écrit : > Hi all. We have a medium size maven deployment. There are about 30 or > 40 projects that the reactor finds in the initial scan. I run the build > in Hudson in 4 steps: > > 1) Mvn clean > > 2) mvn install -Dmaven.test.skip=true > > This finds any bad code and stops the build before going to far, no > tests > > 3) mvn install > > This does the same as above, but now runs the tests (takes > 20 minutes > for this one). > > 4) mvn deploy > > This does the same as above and deploys to our Nexus repository after > each project passes it's tests (again, takes > 20 minutes) > > > > I need to run the 'mvn install' because if I just run the 'mvn deploy', > it starts putting the projects into the Nexus instead of waiting until > all projects pass the build and tests (sometimes the tests fail and I > don't want any of it in the Nexus). > > > > I would like to either: > > > > a) Run the entire mvn build with just the clean and deploy, but > deploy ONLY if all projects build and pass the tests properly > > b) Run the other installs, but when it comes to the deploy, not to > run the install again, just deploy what is already there. > > > > Any ideas? > > > > Thanks, > > mlh > >
