[
https://issues.apache.org/jira/browse/MNG-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738621#comment-14738621
]
Sebastien Arod commented on MNG-1012:
-------------------------------------
The solution proposed by [~dsmiley] seems interesting. It's sad that it was
ignored not even commented.
[~kenneyw] you closed the issue could you please comment on why David's
proposal is not viable?
Having to maintain both relativePath and parent coordinates makes using maven
unintuitive because there is 2 source of truths and painful to synchronize.
I think that is the kind of details that makes maven quite hard to learn and
sometimes annoying to use so that would be nice to find a solution.
> <parent> with only <relativePath> doesn't work
> ----------------------------------------------
>
> Key: MNG-1012
> URL: https://issues.apache.org/jira/browse/MNG-1012
> Project: Maven
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
