[
https://jira.codehaus.org/browse/MNG-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312329#comment-312329
]
Hendy Irawan commented on MNG-1012:
-----------------------------------
I agree with David.
As it stands now, it's pretty annoying and unnecessary. The Parent POM
coordinates are only used in repositories, but not in project *builds*. Please
distinguish those two use cases.
> <parent> with only <relativePath> doesn't work
> ----------------------------------------------
>
> Key: MNG-1012
> URL: https://jira.codehaus.org/browse/MNG-1012
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects 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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
