It seems Maven itself never omits re-doing anything except for downloading artifacts from a remote repository. The command you give to Maven and the configuration of your projects dictates what it will do, no matter what happened in the previous build. You _can_ omit projects in a multi-module project if by manually specifying what projects to run: https://blog.sonatype.com/2009/10/maven-tips-and-tricks-advanced-reactor-options/
Not what you're looking for, but maybe useful: We use one plugin that will skip whole projects that have not changed WRT a given Git branch: https://github.com/vackosar/gitflow-incremental-builder. With careful configuration, this is an effective shortcut without sacrificing repeatability. Gradle advertises as a feature that it will not rebuild if rebuilding is not required, or something to that effect. I assume some configuration required sometimes. On Tue, Feb 4, 2020 at 1:57 PM Anton Vodonosov <[email protected]> wrote: > Ha, only after completing the script (even though a slow one) > I discovered that maven rebuilds modules even if > an artifact of the same version already exists in artifact > repository. > > I hoped maven, in case a non -SNAPSHOT artifact > found in an artifact repository will just use it > and won't build the same version of a module again. > > Is there a way to tell maven to do so? > > Best regards, > - Anton > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --
