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 2003/09/03 15:00:10 UTC
[jira] Updated: (MAVEN-773) artifact plugin messes up target paths [patch]
The following issue has been updated:
Updater: Rafal Krzewski (mailto:rkrzewsk@users.sourceforge.net)
Date: Wed, 3 Sep 2003 7:59 AM
Changes:
Attachment changed to artifact-plugin.diff
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-773&page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-773
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-773
Summary: artifact plugin messes up target paths [patch]
Type: Bug
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: maven
Versions:
1.0-rc1
Assignee:
Reporter: Rafal Krzewski
Created: Wed, 3 Sep 2003 7:57 AM
Updated: Wed, 3 Sep 2003 7:59 AM
Description:
I've started using war:deploy-snapshot goal in my project and I've
discovered a few issues in the artifact plugin that performs the
acutal deployment.
First, the artifacts were deployed to
REPO/groupId/wars/groupId/wars/ directory because of a bug in
FileDeplpoyer (DeployRequest.getDestFile() was being used in place
of DeployRequest.filename())
Second, there was confusion between aftifact files and .md5 files.
With the code you were getting artifact-SNAPSHOT.war and artifact-SNAPSHOT.war.md5 containg the war and artifact-timestamp.war
and artifact-stimestamp.war.md5 containg the md5 sum, this was
happening because two lines were reversed during filling the srcFiles
array.
Third, artifact-currentVersion.pom was deployed alongside artifact-SNAPSHOT.war. artifact-SNAPSHOT.pom should be deployed instead.
The attached patch fixes all three issues above, plus removes some code redundancy by reusing deploy() and deploySnapshot() methods for deploying POM alongside of the artifact.
---------------------------------------------------------------------
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