You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/10/24 21:53:08 UTC
[jira] Moved: (MGPG-32) Deploying snapshot sources with
gpg:sign-and-deploy-file - Is it possible ? It increments build number
[ http://jira.codehaus.org/browse/MGPG-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann moved MNG-4876 to MGPG-32:
--------------------------------------------
Complexity: (was: Intermediate)
Component/s: (was: Deployment)
Affects Version/s: (was: 3.0)
1.1
Issue Type: Improvement (was: Bug)
Key: MGPG-32 (was: MNG-4876)
Project: Maven 2.x GPG Plugin (was: Maven 2 & 3)
> Deploying snapshot sources with gpg:sign-and-deploy-file - Is it possible ? It increments build number
> ------------------------------------------------------------------------------------------------------
>
> Key: MGPG-32
> URL: http://jira.codehaus.org/browse/MGPG-32
> Project: Maven 2.x GPG Plugin
> Issue Type: Improvement
> Affects Versions: 1.1
> 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