On Feb 17, 12:23 pm, Richard Rodseth <[email protected]> wrote: > There's a section here called "A final note on Inheritance v. > Aggregation":http://maven.apache.org/pom.html > > which suggests its not unusual to have POMs that are both parents and > aggregators. The reason I don't like it, is that I'd like to have a parent > pom which captures settings that any Flex project in the company would use, > and that seems to me to be entirely separate from the libs that make up a > particular swf.
Yes, so you create a parent pom with common settings, and the pom for each individual project has it's libs and dependencies. If there are a few libs that all Flex projects use, you can put them in the parent pom if you like. > I suppose some would argue that *all* artifacts should end up back in the > Nexus/Artifactory repository, in which case aggregation (the <modules> tag) > is not needed. I'm not sure I buy that either. All artifacts that are dependencies of another project should be in there, as well as any that are distributed. An aggregator pom doesn't need to be in there, but any parent pom should. > For the moment I'm leaning towards <relativePath> in the <parent> tag. I'm not sure what this buys you, and it does tie you to a particular file system layout (projects are not independently buildable unless the relative parent pom is also in the repo). Sometimes though, it can yield some flexibility. Logan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos?hl=en?hl=en http://blog.flex-mojos.info/ -~----------~----~----~----~------~----~------~--~---
