Hi all, this is kind of a best-practise-question about your habbits of using the concepts of multi-project-super-pom.
First of all, are there distinctive terms commonly agreed upon for each of those concepts? Second, those two ways of using POMs appear to me to be orthogonal to each other, really. Parent POMs are used to define common characterisitics for a group of projects. Multi Project POMs on the other hand aggregate modules belonging to a greater project. I usually have the habbit of defining two diffent poms for multiproject situations. e.g.: /multiproject-pom X -parent-pom Y -module A / pom A (parent pom: Y) -module B / pom B (parent pom: Y) In most examples found though (e.g. in maven's own sources themselfs) typically multi project poms at the same time are used as parent poms for those modules they aggregated. So, what I can't get my head around yet is, is it just a matter of habbit or taste to combine those two usages in just one POM? or am I really missing something important here, if I define two distinctive POMs the way described above. I'm thinking about this for quite a while now and any clarification would be much appreciated. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
