The following comment has been added to this issue:
Author: Arik Kfir
Created: Sun, 8 Aug 2004 12:29 PM
Body:
I disagree. I wouldn't ban entities, but I think the correct solution to project
inheritance is stating its parent project group+artifact IDs. Something like:
<project>
<extend>
<groupId>parentProjectGroup</groupId>
<artifactId>parentProjectArtifact</artifactId>
<version>not sure about this...</version>
</extend>
...
</project>
I believe a POM should be composed of a single file - it is not a source code that can
use "#include" statements (borrowing some c syntax ;-) : it is a POM. A descriptor.
Something else, and should be contained so that it can be passed around freely. It CAN
however contain links to other "beings" such as dependencies, parent projects, etc.
Anyway, that's how we view things over here, and frankly, we'd hate maven to ignore
this issue and simply solve it by using entities - we would love to see some sort of
declarative inheritance in maven - it's like a big chunk of a puzzle...
Cheers..
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1390?page=comments#action_22877
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1390
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1390
Summary: POM example <extends> doco is non-portable
Type: Improvement
Status: Unassigned
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Fix Fors:
1.0.1
Assignee:
Reporter: John Casey
Created: Thu, 22 Jul 2004 12:29 PM
Updated: Sun, 8 Aug 2004 12:29 PM
Description:
In the documentation for the POM, the example includes:
<extends>${basedir}/../project.xml</extends>
which will wreak havoc on any attempts to use the pom without having the parent
project's files on hand. This means that this pom is next to useless, unless we can
first checkout the parent project from scm or somesuch. The scm info is in the POM, so
you see a circle beginning to emerge...
We should change this example to be:
<extends>${maven.repo.local}/${pom.groupId}/poms/${pom.id}-${pom.currentVersion}.pom</extends>
where all pom.* values are filled in manually with the actual values.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
