Hi Nicky,
While I understand the problem that you've presented, I don't think I
understand your question; can you please elaborate?
Thanks,
Noam
On Tue, Mar 27, 2012 at 6:00 PM, Nicky Ramone <[email protected]> wrote:
> Hello.
>
> When you perform an "Artifactory Release Staging", on a 1.0-SNAPSHOT
> artifact, it is released as 1.0 and then the workspace pom is upgraded to
> the next snapshot version, like 1.1-SNAPSHOT.
> The problem is that if you are in a build pipeline, you have other jobs
> that may be interested in working with the released files (i.e., they want
> to deal with 1.0 and not 1.1-SNAPSHOT). For the next POM versions Jenkins
> would pick up the upgraded pom files anyway.
>
> Is there a reason why the POMs are upgraded in the workspace other than to
> check in the modified POMs?
>
> Thanks.
> Cheers.
>
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
>
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
