SNAPSHOT deployment looks broken

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

SNAPSHOT deployment looks broken

Ryan, Scott D

We have noticed when we deploy snapshots using the default settings of
the deploy plugin that the timestamp is not appended to the artifact
name but instead the word SNAPSHOT is added to the artifact name and the
previous SNAPSHOT is overwritten.  The artifact then has a version and
two SNAPSHOT s appended like artifactname-1.0.0-SNAPSHOT-SNAPSHOT.jar .
This causes a number of issue synchronizing versions between various
locations.  I noticed there was some mention of resolution coming in
1.2.1 but it seemed to be around user parameters in the pom rather than
default behaviour of the deploy 2.3 plugin.  I think until the fix for
this is delivered SNAPSHOT may be unusable since I cannot locate them
with the extra SNAPSHOT added on to the end.  

1. Is the fix that is due in 1.2.1 going to address this issue?
2. If so when is 1.2.1 due out or is there a workaround until then?

Thanks again for a great offering.

Scott D. Ryan
Senior Java Developer/Architect

- - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named. If you are not the intended recipient of this message, you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Aurora Loan Services. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.



Reply | Threaded
Open this post in threaded view
|

Re: SNAPSHOT deployment looks broken

Yoav Landman
Administrator
Hi Scott,

The deploy plugin has a "uniqueVersion" parameter, which causes the 2xSNAPSHOT appending problem when set to false (meaning it will produce artifacts ending with SNAPSHOT not with a timestamp). There is an equal POM parameter that can be specified per repository, which causes the same problem when set to false (this is the issue you mention you already noticed).

The deploy plugin (v.2.3 included) has the "uniqueVersion" flag set to true by default, so unless it is overriden somewhere the problem should not surface (deploying snapshots with the default settings has always been trouble-free).

Anyway, the problem has already been fixed for 1.2.1 (for which we will release RCs soon).
As a workaround you can just make sure the configuration of both the deploy plugin and the the target repository has uniqueVersion always set to true (for both this the default value).

HTH,

Yoav

On 4/2/07, Ryan, Scott D <[hidden email]> wrote:

We have noticed when we deploy snapshots using the default settings of
the deploy plugin that the timestamp is not appended to the artifact
name but instead the word SNAPSHOT is added to the artifact name and the
previous SNAPSHOT is overwritten.  The artifact then has a version and
two SNAPSHOT s appended like artifactname-1.0.0-SNAPSHOT-SNAPSHOT.jar .
This causes a number of issue synchronizing versions between various
locations.  I noticed there was some mention of resolution coming in
1.2.1 but it seemed to be around user parameters in the pom rather than
default behaviour of the deploy 2.3 plugin.  I think until the fix for
this is delivered SNAPSHOT may be unusable since I cannot locate them
with the extra SNAPSHOT added on to the end.

1. Is the fix that is due in 1.2.1 going to address this issue?
2. If so when is 1.2.1 due out or is there a workaround until then?

Thanks again for a great offering.

Scott D. Ryan
Senior Java Developer/Architect

- - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named. If you are not the intended recipient of this message, you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Aurora Loan Services. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

Reply | Threaded
Open this post in threaded view
|

Re: SNAPSHOT deployment looks broken

Ryan, Scott D
I found the issue.  The sample that we used for the distribution section contained a blank tag for the uniqueVersion tag.  That caused it to be set to false for some reason.  I would assume a blank tag would yield the default which is true but not the case with the XML parser so <uniqueVersion/> in your XML will cause the tag to be set to false and cause the issue we were seeing.  All is well now.  I hope that the double SNAPSHOT-SNAPSHOT is fixed soon and am looking forward to the 1.2.1 RC's soon.
 

Scott D. Ryan
Senior Java Developer/Architect



From: [hidden email] [mailto:[hidden email]] On Behalf Of Yoav Landman
Sent: Monday, April 02, 2007 3:22 PM
To: [hidden email]
Cc: Li, Yang
Subject: Re: [Artifactory-users] SNAPSHOT deployment looks broken

Hi Scott,

The deploy plugin has a "uniqueVersion" parameter, which causes the 2xSNAPSHOT appending problem when set to false (meaning it will produce artifacts ending with SNAPSHOT not with a timestamp). There is an equal POM parameter that can be specified per repository, which causes the same problem when set to false (this is the issue you mention you already noticed).

The deploy plugin (v.2.3 included) has the "uniqueVersion" flag set to true by default, so unless it is overriden somewhere the problem should not surface (deploying snapshots with the default settings has always been trouble-free).

Anyway, the problem has already been fixed for 1.2.1 (for which we will release RCs soon).
As a workaround you can just make sure the configuration of both the deploy plugin and the the target repository has uniqueVersion always set to true (for both this the default value).

HTH,

Yoav

On 4/2/07, Ryan, Scott D <[hidden email]> wrote:

We have noticed when we deploy snapshots using the default settings of
the deploy plugin that the timestamp is not appended to the artifact
name but instead the word SNAPSHOT is added to the artifact name and the
previous SNAPSHOT is overwritten.  The artifact then has a version and
two SNAPSHOT s appended like artifactname-1.0.0-SNAPSHOT-SNAPSHOT.jar .
This causes a number of issue synchronizing versions between various
locations.  I noticed there was some mention of resolution coming in
1.2.1 but it seemed to be around user parameters in the pom rather than
default behaviour of the deploy 2.3 plugin.  I think until the fix for
this is delivered SNAPSHOT may be unusable since I cannot locate them
with the extra SNAPSHOT added on to the end.

1. Is the fix that is due in 1.2.1 going to address this issue?
2. If so when is 1.2.1 due out or is there a workaround until then?

Thanks again for a great offering.

Scott D. Ryan
Senior Java Developer/Architect

- - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named. If you are not the intended recipient of this message, you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Aurora Loan Services. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

- - - - - - - - - - - - - - - - - - - - - - - - - - This message is intended only for the personal and confidential use of the designated recipient(s) named. If you are not the intended recipient of this message, you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Aurora Loan Services. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.