[ http://jira.codehaus.org/browse/MNG-1012?page=comments#action_65286 ]
David Smiley commented on MNG-1012: ----------------------------------- I understand that it needs to be standalone. Perhaps when a POM is deployed to a repository, the groupId, artifactId, and version could be inserted (dynamically) and the relativePath would be removed. So the published POM and the POM seen by the developer of the project would be slightly different in this respect. With this compromise, we get the best of both worlds. If you need help on an XSLT to do this, contact me. > <parent> with only <relativePath> doesn't work > ---------------------------------------------- > > Key: MNG-1012 > URL: http://jira.codehaus.org/browse/MNG-1012 > Project: Maven 2 > Type: Bug > Versions: 2.0-beta-1 > Reporter: Hao Chen > > > Use the following in child pom.xml > <parent> > <relativePath>../pom.xml</relativePath> > </parent> > Got error: > [INFO] Reason: Missing groupId element from parent element > Why do we need groupId, artifactId, and version? These data are already > contained in ../pom.xml. It should work the same as Maven 1.0 <extends>. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
