> > Concerning the empty "relativePath" element, this will typically be > > empty when you can't guarantee that the parent is in the parent > > directory. it's a common practice to separate the responsibilities of > > the aggregator pom from the parent pom. When that is the case, if you > > don't have the empty "relativePath" element, it will fail. > > > > To make this a bit clearer: if you use a *released* parent pom, it won't have > a > relative path. If this is true in a module, you need an empty element. And the > site plugin may become disoriented. >
It seems that lots of things in the maven world make the assumption that the aggregator pom and the parent pom are one and the same. I've been having trouble with this parent pom resolution issue in the Hudson/Jenkins environment for some time. In these cases, it's the build server's own pom processing that can't seem to be able to resolve where the parent pom is. I think this has improved on newer versions of the build servers though.
