[
http://jira.codehaus.org/browse/MNG-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=240803#action_240803
]
vychtrle commented on MNG-4876:
-------------------------------
I forgot to mention that the parameter uniqueVersion set to "false" doesn't
change a thing...it behaves exactly the same
> Deploying snapshot sources with gpg:sign-and-deploy-file - Is it possible ?
> It increments build number
> ------------------------------------------------------------------------------------------------------
>
> Key: MNG-4876
> URL: http://jira.codehaus.org/browse/MNG-4876
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Deployment
> Affects Versions: 3.0
> Environment: Apache Maven 3.0 (r1004208) and maven 2.2.1, linux,
> nexus repository
> Reporter: vychtrle
>
> I'm deploying snapshot ant its sources with gpg:sign-and-deploy-file, but the
> sources name does always have the value of the following buildnumber. Like
> artifact-timestamp-1.jar and artifact-timestamp-2-sources.jar
> so that if I then have a snapshot dependency, it is looking for
> artifact-timestamp-2.jar instead of artifact-timestamp-1.jar
> I'm not using any build number plugin etc., the pom definitions for this
> artifact is having only credentials.
> I also don't use SCM...
> here is what I do http://pastebin.com/b2F5Ju1s
--
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
