On the other hand... 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. 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. For the moment I'm leaning towards <relativePath> in the <parent> tag. On Tue, Feb 17, 2009 at 11:02 AM, Richard Rodseth <[email protected]>wrote: > I just wanted to follow up on this. > It appears that when a pom looks for its parent pom in the parent > directory, it assumes the name pom.xml. > So if you wish to keep the parent pom and the master pom separate, you need > to > a) specify <relativePath> in the parent tag. > or > b) rename the master pom, and invoke it with -f > or > c) put the parent pom in the Nexus repository > > I think I need to pick up a Maven book. Any favourites? > > > On Fri, Feb 13, 2009 at 1:12 PM, Richard Rodseth <[email protected]>wrote: > >> > And then there's the <modules> tag. >> >>> > <modules> >>> > <module>Lib1</module> >>> > <module>Lib2</module> >>> > <module>App</module> >>> > </modules> >>> These are the children. They should have a <parent> entry pointing >>> back to this pom. >> >> >> Not in my current build. In the root directory (parent of all projects) is >> a pom (stored in subversion , but not in Artifactory) that contains a >> modules tag. That is the pom that we currently execute. The individual poms >> do not have any reference back to the "master pom". They do have the >> reference to the flex mojos super-pom. >> >> >>> Does that make more sense? >>> >> >> It helps somewhat. I didn't realize the super-pom could be in the parent >> directory on the file system (though that wouldn't help other company >> projects in a different location). But I might still be inclined to keep the >> super-pom and master-pom separate. Conflating the super-pom with the >> master-pom is a little confusing to me, sort of like confusing OO >> inheritance and composition. >> >> Thanks again. >> >> >> >>> >>> >>> >> > --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
