You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "vychtrle (JIRA)" <ji...@codehaus.org> on 2010/10/24 18:49:05 UTC
[jira] Created: (MNG-4876) Deploying snapshot sources with
gpg:sign-and-deploy-file - Is it possible ? It increments build number
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
RE: [jira] Commented: (MNG-4876) Deploying snapshot sources with
gpg:sign-and-deploy-file - Is it possible ? It increments build number
Posted by Saket Lakshminarayan Chiluveru <Sa...@infosys.com>.
Hi,
Please unsubscribe me. It has been very helpful
Regards
Saket
-----Original Message-----
From: vychtrle (JIRA) [mailto:jira@codehaus.org]
Sent: Sunday, October 24, 2010 10:35 PM
To: issues@maven.apache.org
Subject: [jira] Commented: (MNG-4876) Deploying snapshot sources with gpg:sign-and-deploy-file - Is it possible ? It increments build number
[ 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
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are not
to copy, disclose, or distribute this e-mail or its contents to any other person and
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken
every reasonable precaution to minimize this risk, but is not liable for any damage
you may sustain as a result of any virus in this e-mail. You should carry out your
own virus checks before opening the e-mail or attachment. Infosys reserves the
right to monitor and review the content of all messages sent to or from this e-mail
address. Messages sent to or from this e-mail address may be stored on the
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
[jira] Commented: (MNG-4876) Deploying snapshot sources with
gpg:sign-and-deploy-file - Is it possible ? It increments build number
Posted by "vychtrle (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Closed: (MGPG-32) Deploying snapshot sources with
gpg:sign-and-deploy-file - Is it possible ? It increments build number
Posted by "vychtrle (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MGPG-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
vychtrle closed MGPG-32.
------------------------
Resolution: Not A Bug
It was more of a feature request
> 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
[jira] Moved: (MGPG-32) Deploying snapshot sources with
gpg:sign-and-deploy-file - Is it possible ? It increments build number
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ 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