Hi Sartisty, > How to use the latest release version, not modify plugin version in > pom.xml frequently?
Why not just keep it as an eternal 1.0.0-SNAPSHOT or some such? Then you'll never have to change the POMs that use it. But as Baptiste points out, all of those downstream projects will sacrifice build reproducibility. Imagine that you accidentally introduce a bug into your build plugin which starts failing the build erroneously. Then suddenly, projects which use that plugin might have failing builds with no code changes. Release tags that built yesterday will no longer build. Not a good situation! Regards, Curtis On Tue, May 27, 2014 at 3:31 AM, Sartisty <[email protected]> wrote: > hi, all, > I have developed a maven build plugin and I will upgrade it > frequently. How to use the latest release version, not modify plugin > version in pom.xml frequently? One idea is no version setting, but it > will generate too much warnings. Setting LATEST, it won't work. > Is there any good solution? Glad to hear it. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
