Hmm. Not sure I follow. What works out fine? You mean that if the name of the artifact ID is the name as the directory, the SCM section does not get inheritied??
Are you suggesting that a parement POM should only be referenced by a project only if that project is a child module of the parent POM? What if you want to reference a parent POM that isn't the parent of a child module? For instance, when defining a corporation wide super POM. --- Todd Thiessen > -----Original Message----- > From: Wendy Smoak [mailto:[email protected]] > Sent: Monday, December 15, 2008 1:35 PM > To: Maven Users List > Subject: Re: POM Private Inheritence > > On Mon, Dec 8, 2008 at 8:31 AM, Todd Thiessen > <[email protected]> wrote: > > > http://maven.apache.org/pom.html#Inheritance > > > > it sounds like only certain sections of the POM get inheritied. For > > instance, the SCM section is one section that is NOT mentioned as > > inherited. > > From experience, the scm section does get inherited as a base > url, then the artifactId of the child module is added. If > you follow the convention that the directory name matches the > artifactId, it all works out fine. > > If not, then you need to override the scm element in each pom > that does not conform. > > You always need to have a scm element at the 'top' of each > directory tree, because the parent's scm urls won't be useful > as a base. > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
