I actually created the redundancy on purpose. Its just a few lines that aren't likely to change soon. I would rather have the few lines repeated in two poms instead of creating a new dependency.
The master pom has several reports defined along with the list of developers and some other useful stuff. Since the committer/pmc list, etc. sometimes change and since its so large it makes sense to have it in a master pom. Sean On 2/14/06, Manfred Geiler <[EMAIL PROTECTED]> wrote: > On 2/14/06, Sean Schofield <[EMAIL PROTECTED]> wrote: > > > Q1. Regarding the maven sub-project: Why do build-tools and master-pom > > > have no parent relationship to the maven-project pom? > > > > There is nothing that needs to really be shared between the two. More > > importantly, since every other subproject starts out with the > > master-pom, you would basically require all of > > those projects to depend on the maven-project pom. This would be > > another extra artifact that you would have to publish and maintain > > (for no good reason.) > > Well, there is exactly one good reason which is also the reason why > I'm asking ;-) > DistributionManagement is currently defined in redundant places which > shouldn't be so IMHO. The easiest thing would be to eleminate > distributionManagement info from every pom other than the > maven-project pom. But this would only work if master-pom and > build-tools would be derived from maven-project pom. > > Manfred >
