An application that uses the components does not need to be a parent and specify the components as modules. It can just be another module, and specify the components it needs as dependencies. Then your POM that defines the modules is just there to help build all at once.
If you want to be able to build separtely, but still need to be able to build the components the same time as the app that uses them, then you can create separate POM's with different modules defined. You can run "mvn -f pom2.xml install" to build the modules defined in pom2.xml In my "modules", the "parent" is not the POM in the directory above that aggregates the multi-project. It's a totally separate POM that defines shared configuration and dependencies. So you don't even have to specify a "parent" if you don't wish to. So that gets rid of your concern about multiple parents. -Stephen On 2/8/06, Helck, Christopher <[EMAIL PROTECTED]> wrote: > Hi, > > Currently we have one application that is divided into six components. > We build the entire thing using maven1's multiproject goals. Our > certification team is happy with this because they just need to type one > command and everything builds. > > We are now creating a second application that will reuse some of the > components and I can't figure out how to support simple builds for both > application. Basically I want to treat the six components as indepent > entities -- if Component X is changed, we update its version number, > build/deploy, and update the application's pom to use the new version. > This is ok for developer's but I imagine the certification team will > have a fit. They want simple builds. > > I looked at maven2's modules support. It seems to me that I should > define a pom for each of my applications and these poms should list the > modules they need to build. Each component should then include a > <parent/> tag describing the application they belong to. One problem is > the modules have multiple parents which does not work. Another problem > is that the applications may use different versions of the same > component. This doesn't even make sense. > > To be fair, I don't know if the problem is with maven. Our certification > people want to build all of the software, but they are use to doing it > at the end of a project with one command. How are people dealing with > problems like this? > > Thanks, > Christopher Helck > > > > Thank you for being part of it. > > The information contained in this e-mail is confidential. This e-mail is > intended only for the stated addressee. If you are not an addressee, you > must not disclose, copy, circulate or in any other way use or rely on the > information contained in this e-mail. if you have received this e-mail in > error, please inform us immediately and delete it and all copies from your > system. > > EBS Dealing Resources International Limited. Registered address: 10 > Paternoster Square, London EC4M 7DY, United Kingdom. Registered number > 2669861. > > EBS Dealing Resources, Inc, registered in Delaware. Address: 535 Madison > Avenue, 24th Floor, New York, NY 10022, USA, and One upper Pond road, > Building F - Floor 3, Parsippany, NJ 07054, USA. > > EBS Dealing Resources Japan Limited, a Japanese Corporation. Address: Asteer > Kayabacho Bldg, 6th Floor, 1-6-1, Shinkawa, Chuo-Ku, Tokyo 104-0033, Japan. > > > -- Stephen Duncan Jr www.stephenduncanjr.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
