[ http://jira.codehaus.org/browse/MDEPLOY-33?page=all ]
John Casey closed MDEPLOY-33:
-----------------------------
Resolution: Fixed
had to pass the pomFile (generated or provided) to the artifactDeployer instead
of the main project artifact file...this artifact file is passed to the
artifact using setFile(..), and the artifactDeployer call takes both the
pomFile and the artifact now.
NOTE: I simply copied the API calls in the main DeployMojo to fix this.
> [deploy-file] When deploying a snapshot version with the pomFile specified,
> POM and artifact get different build numbers
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: MDEPLOY-33
> URL: http://jira.codehaus.org/browse/MDEPLOY-33
> Project: Maven 2.x Deploy Plugin
> Type: Bug
> Versions: 2.2
> Reporter: John Casey
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.3
>
> Original Estimate: 10 minutes
> Remaining: 10 minutes
>
> the call to the ArtifactDeployer is not setup correctly to handle the case
> where a POM is specified (not generated). It should deploy the snapshot POM
> and artifact with the same build number, and this is currently not the case.
--
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
