The following comment has been added to this issue:
Author: Rafal Krzewski
Created: Tue, 3 Feb 2004 8:53 AM
Body:
valid concern, wrong solution. this has been discussed repetadely before. the clean
solution is:
<extend>
<artifactId>...</artifactId>
<groupId>...</groupId>
<version>...</version>
</extend>
that would fetch the super project from repository as necessary.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPARTIFACT-10&page=comments#action_16377
---------------------------------------------------------------------
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: Tue, 3 Feb 2004 8:53 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]
