The following comment has been added to this issue:
Author: Rafal Krzewski
Created: Wed, 4 Feb 2004 4:41 AM
Body:
Indeed, the super project pom needs to be installed locally, or deployed to some
available repository before sub projects may be built, but I think it is a fair
requirement. You generaly need to create stuff before you are able to use it :-).
I don't think that this solution may introduce any additional circular dependency
problems. If you define a dependency on a sub-project in your super project, you are
hosed regardles of how you reference the super project in sub project.
Also, maven does not suport "rebuilding (dependant) artifacts on demand". It has no
means of determining if the *demand* exists, except for explicit user instruciton.
Maven is like Ant, not make in this regard. I hope that we'll be able to leverage 30
years of experience of the make community eventualy, but there is a *ton* of other
issues to be taken of first.
As for acceptance of this <extend> scheme, at least Jason and Michal said it was OK,
but there were no specific plans for implementing it. It probably won't happen until
after 1.0 is out and the new componetized codebase arrives.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPARTIFACT-10&page=comments#action_16415
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPARTIFACT-10
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPARTIFACT-10
Summary: artifact:install doesn't resolve references in pom files
Type: Improvement
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-artifact-plugin
Versions:
1.0
Assignee:
Reporter: Ralf Stoffels
Created: Tue, 3 Feb 2004 8:28 AM
Updated: Wed, 4 Feb 2004 4:41 AM
Description:
artifact:install copies the project.xml file without any
modifications to the repository.
This entails that the extend element looses its reference.
Therefore all references to the extended project
(like ${pom.groupId}) are dangling and can't be resolved anymore.
artifact:install should resolve these references before copying.
---------------------------------------------------------------------
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]
