You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Hao Chen (JIRA)" <ji...@codehaus.org> on 2005/09/24 00:10:11 UTC
[jira] Created: (MNG-1012) with only doesn't work
<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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-1012) with only doesn't work
Posted by "Kenney Westerhof (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1012?page=all ]
Kenney Westerhof closed MNG-1012:
---------------------------------
Resolution: Won't Fix
[copied more or less from a mail to the user-list]
The artifactId, groupId and version are mandatory in a <parent> element.
POMs should be able to be used stand-alone. A client that uses your pom
wouldn't know where to look for that parent pom, since the directory
structure on ibiblio is not quite the same as the project tree structure.
Before this attribute was in, m2 always checked ../pom.xml to see if it
matched the declared parent. If so, it used that (and the data in
target/*) instead of going to your local/remote repositories for the pom.
This attribute is just an extension to that, so you can specify
other locations for your parent project than ../.
It is not and will not be a replacement for <extends> in maven1.
> <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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org