[jira] Commented: (MAVEN-1390) POM example doco is non-portable

2004-08-08 Thread jira
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: pare

[jira] Commented: (MAVEN-1390) POM example doco is non-portable

2004-07-23 Thread jira
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 ../pro

[jira] Commented: (MAVEN-1390) POM example doco is non-portable

2004-07-23 Thread jira
The following comment has been added to this issue: Author: Brett Porter Created: Fri, 23 Jul 2004 12:08 PM Body: that's a tangent to the original issue. Yes, entities should be resolved if they are supported. - V

[jira] Commented: (MAVEN-1390) POM example doco is non-portable

2004-07-23 Thread jira
The following comment has been added to this issue: Author: Joerg Schaible Created: Fri, 23 Jul 2004 11:58 AM Body: duplicated now by MPPOM-4 and would also resolve MPPOM-1 - View this comment: http://jira.codeha

[jira] Commented: (MAVEN-1390) POM example doco is non-portable

2004-07-23 Thread jira
The following comment has been added to this issue: Author: Joerg Schaible Created: Fri, 23 Jul 2004 11:34 AM Body: But then you have to prevent people using entities or properties in a POM at all: &my-comp-version; is as evil than ${my.comp.version} Maybe it's just me, but I

[jira] Commented: (MAVEN-1390) POM example doco is non-portable

2004-07-23 Thread jira
The following comment has been added to this issue: Author: Brett Porter Created: Fri, 23 Jul 2004 11:11 AM Body: not compatible with the long term goal of building the structure from POMs that reside in the repository. -

[jira] Commented: (MAVEN-1390) POM example doco is non-portable

2004-07-23 Thread jira
The following comment has been added to this issue: Author: Joerg Schaible Created: Fri, 23 Jul 2004 11:01 AM Body: Brett: Then why not deploy the resolved POM? No expand problem, no entity headache and anything is included and does not have to reference any external file. ---

[jira] Commented: (MAVEN-1390) POM example doco is non-portable

2004-07-23 Thread jira
The following comment has been added to this issue: Author: Brett Porter Created: Fri, 23 Jul 2004 10:51 AM Body: Joerg: it's chicken and the egg. If we add a dependency to the project it would be downloaded, but dependencies aren't done until the extended element is read. That i

[jira] Commented: (MAVEN-1390) POM example doco is non-portable

2004-07-23 Thread jira
The following comment has been added to this issue: Author: Joerg Schaible Created: Fri, 23 Jul 2004 4:56 AM Body: And how would you develop in a multiproject? If someone checks out from the repository, he has no "parent" pom in the local repo, nor is it copied there.