The following comment has been added to this issue:
Author: John Casey
Created: Fri, 23 Jul 2004 12:18 PM
Body:
Even if we're writing a clean, "standalone" pom to the repo, there is still the
portability question for the sources themselves.
A good example of the failing of ../project.xml is in the old jakarta-commons stuff.
It's not like this anymore, but it used to be that you had to co the entire
jarkarta-commons module (or at least the root of the module) in order to build any of
the subprojects. This is simply an unwieldy way of doing things, and should be
discouraged regardless of what we decide to do with pom:install and pom:deploy.
Entities should be left out of the equation IMO, but they are currently the best
solution in some cases, and if you're bent on using them then the entity definition
file should be in the project root, because this file will not be deployed to any repo
and will lead to the extends problem all over again if in ../deps.ent f.e. However, if
you follow that rule, then all should be well with entities.
We should also be dealing with "best practices" relating to entities in the doco, once
we get MPPOM-4 figured out. I know some people hate the idea of using entities, but
they're the cleanest solution without having transitive dep resolution in place.
Instead of banning them, and dealing with a "black market" we need to address them and
state a concrete position and usage rule in the documentation - legalize and tax, so
to speak. ;)
These issues - MPPOM-4 and this one - are not in competition, I think, but
complementary.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1390?page=comments#action_22201
---------------------------------------------------------------------
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: Fri, 23 Jul 2004 12:18 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]
