[
https://issues.apache.org/jira/browse/MDEPLOY-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965582#comment-17965582
]
Olivier Lamy commented on MDEPLOY-112:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#272|https://github.com/apache/maven-deploy-plugin/issues/272].
> deployed snapshot name has different build numbers for multiple artifacts of
> the same build
> -------------------------------------------------------------------------------------------
>
> Key: MDEPLOY-112
> URL: https://issues.apache.org/jira/browse/MDEPLOY-112
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Components: deploy:deploy
> Affects Versions: 2.2.1
> Environment: windows xp
> Reporter: Gabriel Dogaru
> Assignee: Benjamin Bentmann
> Priority: Major
> Fix For: 2.6
>
>
> I have a module that deploys 2 artifacts,1 jar and 1 of them is custom type.
> The build number from the snapshot name is different for the 2 (in the
> repository). It get incremented every time an artifact is deployed. When I
> try to make a local build it searches for the highest build number, and tries
> to bring both the artifacts with the latest build number but only one of them
> has that number.
> I found a workaround for this by <uniqueVersion>false</uniqueVersion> for
> the snapshotRepository.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
