You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@codehaus.org> on 2011/08/22 10:44:32 UTC
[jira] Commented: (MDEPLOY-67) altDeploymentRepository causes build
numbers in snapshots to not be incremented
[ https://jira.codehaus.org/browse/MDEPLOY-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276642#comment-276642 ]
Stephen Connolly commented on MDEPLOY-67:
-----------------------------------------
First step would be if somebody can create a test case.
> altDeploymentRepository causes build numbers in snapshots to not be incremented
> -------------------------------------------------------------------------------
>
> Key: MDEPLOY-67
> URL: https://jira.codehaus.org/browse/MDEPLOY-67
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: Brian Fox
> Labels: contributers-welcome
>
> I haven't looked in detail to this, but I think the deploy plugin is pulling the metadata from the original distMgt repo and not the altDeployone. The symptom is that all my snapshots end in -1 (i don't know if metadata corruption could occur on releases). As soon as I threw out this feature and used distMgt over rides in a profile, the build numbers started working.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira