Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0-rc1
-
Fix Version/s: 1.0-rc1
-
Component/s: None
-
Labels:None
-
Number of attachments :
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.
Already applied by Rafal on 2003-09-06