Hi.
We are using the Jenkins plugin to stage our artifacts.
With the way we work with our versions, we don't want the "next
development" version to be incremented, so in the "Release Staging" screen,
we just pick the same version as before.
For example, if we are staging 1.0.0-SNAPSHOT, then
Release version: 1.0.0-54
Next development version: 1.0.0-SNAPSHOT
Artifactory commits changes to the development POM even in that case.
Besides triggering a new unnecessary build, this is causing us a few issues
(I will detail them somewhere else).
Would it be possible to fix this so that it doesn't commit the POM if the
version is not modified?
Thanks.
Regards.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
