> 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/ -~----------~----~----~----~------~----~------~--~---
