Ok.. now this makes more sense to me :-) See here for how to block overwriting of artifacts. https://stackoverflow.com/questions/6461152/how-can-i-prevent-previously-deployed-artifacts-from-being-overwritten
Christian On 27.06.2017 09:28, Tom Quarendon wrote:
I'm not *wanting* to allow overwriting release versions, that is kind of the point. But, out of the box, an artifactory maven (release) repository appears to allow this. And there's no configuration option that I can find that says "don't allow overwriting versions". It's not obvious to me, not having that much experience with maven, whether this is "right" or "wrong". I *think* that the maven view of the world is that there is one, unique, artefact with any given (non-snapshot) version number, and therefore that any two artifacts that you might see with the same (non-snapshot) coordinates are to be considered equivalent. The corollary of that is that versions are (should be) immutable. But if that is the case, then artifactory breaks that rule by allowing you to overwrite released versions. As I say, my understanding of maven is shallow. Relying on uniqueness of git tags seems like the most profitable route, assuming I can understand how I ensure that that check is done before the upload actually happens.
-- Christian Schneider http://www.liquid-reality.de Open Source Architect http://www.talend.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
