[
https://issues.apache.org/jira/browse/MDEPLOY-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965560#comment-17965560
]
Olivier Lamy commented on MDEPLOY-33:
-------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#132|https://github.com/apache/maven-deploy-plugin/issues/132].
> [deploy-file] When deploying a snapshot version with the pomFile specified,
> POM and artifact get different build numbers
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: MDEPLOY-33
> URL: https://issues.apache.org/jira/browse/MDEPLOY-33
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: John Dennis Casey
> Assignee: John Dennis Casey
> Priority: Critical
> Original Estimate: 10m
> Remaining Estimate: 10m
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
