Hi Charles & everyone, > To prevent SNAPSHOT churn you can use a plugin like > exists-maven-plugin > (https://chonton.github.io/exists-maven-plugin/0.0.2/plugin-info.html > <https://chonton.github.io/exists-maven-plugin/0.0.2/plugin-info.html>) > to prevent re-releasing unchanged artifacts.
Thanks for the suggestion. I think exists-maven-plugin is really useful for some scenarios. However, I want to comment that I think one should not use exists-maven-plugin in this way to address a symptom—400 forbidden errors when redeploying same version to remote repository—rather than the root problem of having two commits with the same release version number. With this scheme, any time you build a commit from the history including the "install" phase (e.g., if testing something with "git bisect"), you may end up overwriting the release version in your local repository cache with something which is _not_ actually the release build of the component. So I think it is dangerous to lean on exists-maven-plugin in this way. I actually _want_ the build to fail in the CI at the deploy step, to give me a heads up that there are two commits like this, so that the problem can be fixed before even more commits are made at that same version number. Regards, Curtis -- Curtis Rueden LOCI software architect - https://loci.wisc.edu/software ImageJ2 lead, Fiji maintainer - https://imagej.net/User:Rueden On Mon, Apr 24, 2017 at 9:09 PM, Charles Honton <c...@honton.org> wrote: > To prevent SNAPSHOT churn you can use a plugin like exists-maven-plugin ( > https://chonton.github.io/exists-maven-plugin/0.0.2/plugin-info.html < > https://chonton.github.io/exists-maven-plugin/0.0.2/plugin-info.html>) to > prevent re-releasing unchanged artifacts. > > chas > > > On Apr 24, 2017, at 1:52 PM, Curtis Rueden <ctrue...@wisc.edu> wrote: > > > > because every release concludes > > with a "bump to next development cycle" commit > >
