Since I use Eclipse I have to sort of flatten out the project structure. So the structure looks like this:
base + build (this is parent, children are ../ear and ../war1 and so forth) + ear (parent is ../build) + war1 (ditto) + war2 + jar1 + jar2 I just put the common files, license.txt, checkstyle.xml, etc, in the base folder. Some cases allow just referring to the common file in build/pom.xml (which is the parent of all the others). The reference is just ../checkstyle.xml or whatever. Anywhere else I need them they are still ../checkstyle.xml. -- Lee On 12/28/05, Scokart Gilles <[EMAIL PROTECTED]> wrote: > > Two idea : > - Refactor in order to be able to place those resources into a separated > module used as a dependency by the other "subproject". > - If not possible, see if you can use links into your repository (need > unix > like platform) > > > > -----Original Message----- > > From: Daniel Kulp [mailto:[EMAIL PROTECTED] > > Sent: 28 December 2005 15:59 > > To: Maven Users List > > Subject: M2: Subprojects and common resources.... > > > > > > What is the best way to deal with "common" resources used by several > > subprojects? We have a bunch of stuff like checkstyle config files, > > pmd rulesets, logging config properties files, etc... that we would like > > to be used by all the subprojects. The only way seems to be to copy > the > > resources into each subproject. That really sucks from a management > > standpoint. > > > > Thanks! > > -- > > J. Daniel Kulp > > Principal Engineer > > IONA > > P: 781-902-8727 C: 508-380-7194 > > [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > > 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] > > -- -- Lee Meador Sent from gmail. My real email address is [EMAIL PROTECTED]
