Multiproject release builds -- how to do?

[Erik Husby]

I want to have a multiproject build produce a release for my application 
A, which depends on component B. I check out the sources from CVS so 
that I end up with a two directories in my workarea, A, B. I want to be 
able to issue a build command from A that will also build B. Sounds 
reasonable does it not.

But, Maven says dependency B-1.0.jar does not exist and refuses to 
build. Well of course B-1.0.jar does not exist because it has not been 
built yet!

I don't want to write a shell script to first build B and then A because 
Maven multiproject is supposed to do that for me. Is there away to force 
the multiproject build to go ahead with unsatisfied dependencies?

--
Erik Husby
Team Lead for Software Quality Automation
Broad Institute of MIT and Harvard 
Rm. 2192  320 Charles St, Cambridge, MA 02141-2023
mobile: 781.354.6669, office: 617.258.9227, 
email: [EMAIL PROTECTED]  AIM: ErikAtBroad

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]