This probably should be the behaviour (as long as the SCM is laid out like your local copy is, which isn't strictly necessary, eg with SVN externals, but the same fallback is there - to specifically define the URL in the child POM).
Would you like to file it in JIRA? - Brett On 11/24/05, Christian Schulte <[EMAIL PROTECTED]> wrote: > Hi, > > I have severe problems with the flat project layout as described at > <http://maven.apache.org/guides/mini/guide-ide-eclipse.html> at the end > of the site. As it seems inheritance is not supporting the relative path > and modules settings. Somewhere in here > > <http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/inheritance/DefaultModelInheritanceAssembler.java?view=markup> > > maven 2 definetely ignores the values of the parent <modules> > definitions during building e.g. SCM-URLs. My question is, if there is > any reason why this is done that way. It seems straightforward to change > this class so that SCM-URLs and URLs in general would be inherited > correctly e.g. use the value of the parent's <module>...</module> > definition instead of just adding the child's artifactID to the end of > the parent's URLs. > > So what is the reason why the values of the <modules>...</modules> are > ignored completely ? Would it break anything if only this class > (DefaultModelInheritanceAssembler) would honour the > <modules>...</modules> definitions of the parent ? > > -- > Christian > > > --------------------------------------------------------------------- > 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]
