You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/07/22 18:31:10 UTC
[jira] Created: (MAVEN-1390) POM example doco is non-portable
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
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
Assignee:
Reporter: John Casey
Created: Thu, 22 Jul 2004 12:29 PM
Updated: Thu, 22 Jul 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1390) POM example doco is non-portable
Posted by ji...@codehaus.org.
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 issue would need to be resolved some way.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1390?page=comments#action_22185
---------------------------------------------------------------------
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 10:51 AM
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MAVEN-1390) POM example doco is non-portable
Posted by ji...@codehaus.org.
The following issue has been updated:
Updater: Brett Porter (mailto:brett@codehaus.org)
Date: Thu, 23 Sep 2004 3:03 AM
Changes:
environment changed to
priority changed to Blocker
Fix Version changed to 1.1
Fix Version changed from 1.0.1
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MAVEN-1390?page=history
---------------------------------------------------------------------
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
Priority: Blocker
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Fix Fors:
1.1
Assignee:
Reporter: John Casey
Created: Thu, 22 Jul 2004 12:29 PM
Updated: Thu, 23 Sep 2004 3:03 AM
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MAVEN-1390) POM example doco is non-portable
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1390?page=all ]
Brett Porter closed MAVEN-1390:
-------------------------------
Resolution: Won't Fix
Fix Version: (was: 1.1-rc1)
now that we deploy the resolved pom, this is unnecessary for that use case.
It's still an issue for checking out projects in isolation, but the feature is present in m2.
> POM example <extends> doco is non-portable
> ------------------------------------------
>
> Key: MAVEN-1390
> URL: http://jira.codehaus.org/browse/MAVEN-1390
> Project: Maven
> Type: Improvement
> Reporter: John Casey
> Priority: Blocker
>
>
> 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.
--
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] Commented: (MAVEN-1390) POM example doco is non-portable
Posted by ji...@codehaus.org.
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.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1390?page=comments#action_22190
---------------------------------------------------------------------
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 11:11 AM
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1390) POM example doco is non-portable
Posted by ji...@codehaus.org.
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1390) POM example doco is non-portable
Posted by ji...@codehaus.org.
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.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1390?page=comments#action_22187
---------------------------------------------------------------------
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 11:01 AM
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MAVEN-1390) POM example doco is non-portable
Posted by ji...@codehaus.org.
The following issue has been updated:
Updater: Brett Porter (mailto:brett@codehaus.org)
Date: Fri, 23 Jul 2004 2:20 AM
Changes:
Fix Version changed to 1.0.1
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MAVEN-1390?page=history
---------------------------------------------------------------------
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 2:20 AM
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1390) POM example doco is non-portable
Posted by ji...@codehaus.org.
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1390) POM example doco is non-portable
Posted by ji...@codehaus.org.
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.codehaus.org/browse/MAVEN-1390?page=comments#action_22197
---------------------------------------------------------------------
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 11:58 AM
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1390) POM example doco is non-portable
Posted by ji...@codehaus.org.
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.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1390?page=comments#action_22200
---------------------------------------------------------------------
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:08 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MAVEN-1390) POM example doco is non-portable
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1390?page=all ]
Brett Porter updated MAVEN-1390:
--------------------------------
Fix Version: (was: 1.1-beta-1)
1.1-beta-2
> POM example <extends> doco is non-portable
> ------------------------------------------
>
> Key: MAVEN-1390
> URL: http://jira.codehaus.org/browse/MAVEN-1390
> Project: maven
> Type: Improvement
> Reporter: John Casey
> Priority: Blocker
> Fix For: 1.1-beta-2
>
>
> 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.
--
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] Updated: (MAVEN-1390) POM example doco is non-portable
Posted by ji...@codehaus.org.
The following issue has been updated:
Updater: Brett Porter (mailto:brett@codehaus.org)
Date: Thu, 2 Dec 2004 9:43 PM
Changes:
Fix Version changed to 1.1-beta-1
Fix Version changed from 1.1
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/browse/MAVEN-1390?page=history
---------------------------------------------------------------------
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
Priority: Blocker
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Fix Fors:
1.1-beta-1
Assignee:
Reporter: John Casey
Created: Thu, 22 Jul 2004 12:29 PM
Updated: Thu, 2 Dec 2004 9:43 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1390) POM example doco is non-portable
Posted by ji...@codehaus.org.
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:
<version>&my-comp-version;</version>
is as evil than
<version>${my.comp.version}</version>
Maybe it's just me, but I cannot follow the argumentation. Why does a resolved POM (i.e. no external references at all and all inherited tags embedded) interfere with that long term goal? The deployed POM would contain any information.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1390?page=comments#action_22193
---------------------------------------------------------------------
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 11:34 AM
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MAVEN-1390) POM example doco is non-portable
Posted by ji...@codehaus.org.
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.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1390?page=comments#action_22168
---------------------------------------------------------------------
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 4:56 AM
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MAVEN-1390) POM example doco is non-portable
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVEN-1390?page=all ]
Brett Porter updated MAVEN-1390:
--------------------------------
Fix Version: (was: 1.1-beta-2)
1.1-rc1
> POM example <extends> doco is non-portable
> ------------------------------------------
>
> Key: MAVEN-1390
> URL: http://jira.codehaus.org/browse/MAVEN-1390
> Project: Maven
> Type: Improvement
> Reporter: John Casey
> Priority: Blocker
> Fix For: 1.1-rc1
>
>
> 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.
--
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