[ https://issues.apache.org/jira/browse/MNG-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hervé Boutemy reopened MNG-5821: -------------------------------- reopening the issue Arthur is right, maven-4.0.0.xsd in site is outdated: see http://maven.apache.org/xsd/ {noformat} maven-4.0.0.xsd 2012-12-11 13:48{noformat} current 3.3.3 documentation = http://maven.apache.org/ref/3.3.3/maven-model/maven.html#class_parent but xsd was put in the site in 2012, and seems to have been generated even before see https://svn.apache.org/viewvc/maven/site/trunk/content/resources/xsd/ I'll move this issue to MNGSITE (since this is a site issue) and update the xsd with a recently generated one, taken from current source HEAD (and in fact, perhaps we should publish the xsd sometimes, since we don't update elements but we update documentation/comments in it) > Documentation of the element parent.relativePath wrong in XSD > ------------------------------------------------------------- > > Key: MNG-5821 > URL: https://issues.apache.org/jira/browse/MNG-5821 > Project: Maven > Issue Type: Documentation > Reporter: Arthur Bauer > Assignee: Karl Heinz Marbaise > Attachments: mvn-3.0.5.log, mvn-3.1.1.log, mvn-3.2.5.log, > mvn-3.3.3.log, test.zip > > > The documentation of the element parent.relativePath in the XSD file seems to > be wrong or outdated. It says: > "Maven looks for the parent pom first in the reactor of currently building > projects, then in this location on the filesystem, then the local repository, > and lastly in the remote repo." > (Source: http://maven.apache.org/xsd/maven-4.0.0.xsd) > But the actual documentation of maven says > "Maven looks for the parent POM first in this location on the filesystem, > then the local repository, and lastly in the remote repo." > (Source: > http://maven.apache.org/ref/3.0.3/maven-model/apidocs/org/apache/maven/model/Parent.html#getRelativePath%28%29) > I have tested it on my local and I have seen the behavior as described in the > second source, i.e. maven does not look for the parent pom in the reactor of > currently building projects first. > So this is pretty misleading. It is even more misleading for us, as we are > reading the documentation directly from eclipse, which loads it from the XSD > file. > Could you please correct the XSD documentation? -- This message was sent by Atlassian JIRA (v6.3.4#6332)