Marek Chowaniok wrote on Tuesday, October 10, 2006 11:22 AM: > Thanks Jorg, > if I understand it corectly than > product-web-customer will have in pom.xml <packaging>pom</packaging> > and the 3 others will have in pom.xml <packaging>war</packaging> > and those 3 will have dependecy on the parent ?
No, all are wars. Keep the common stuff in one and make the others depednend on it. - Jörg > > thanks > > > > > > Jörg Schaible wrote: >> >> Marek Chowaniok wrote on Tuesday, October 10, 2006 7:36 AM: >> >>> We have separate projects (i.e.product-web-customer, >>> product-web-customer1 and product-web-customer2) with just the >>> different files. i.e. we have 20 jsp pages but just the 2 are >>> defferent and are in separate projects. >>> >>> Right now (not using maven in this project yet) we have to do deploy >>> for product-web-customer and replace files in this deploy with >>> concrete jsp files from different project. >>> >>> I am just starting using maven, so I don't know what the proper way >>> how to do it. And how maven usually handle this situation. >>> >>> So is there something that I would do deploy for >>> product-web-customer and >>> tell maven to add/replace some JSP from different customer project ? >> >> Generate a war artifact for the common stuff and 3 ones for the >> different customers. Let those be dependend on the common war, it >> will merged into the customer's ones. >> >> - Jörg >> >> > --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
