I can offer some experience with Takari Lifecycle. I am using it in my
smallish srcdeps project . I took it for its seamless integration
with Eclipse Sisu rather than for its incremental builds.
Takari is a replacement for the default Maven Lifecycle - i.e. Takari
replaces the default Maven plugins (compile, resources, jar, ...) with
its own variants. While their plugins serve the same purpose as the
default ones, the configuration may (an often is) not as rich as with
the default plugins. One prominent example is that they do not support
war packaging .
Hence when deciding whether Takari is a good choice one should in the
first place check carefully if their plugins support all necessary
configuration options. I am not sure if their incrementality claims
still hold when non-takari plugins are executed during the build.
As for their incremental compilation, they say  they can do it thanks
Eclipse Java Compiler (a.k.a. JDT Compiler). It is known that JDT
Compiler and OpenJDK's javac sometimes differ in what Java source they
accept . That might be seen as an argument against using JDT Compiler
and Takari inside CI.
It's been a while, so I can't offer any precise numbers on this, but for a
while I tried doing incremental builds of Camel on the Fuse Jenkins.
Sometimes this would result in a relatively quick (45min to 1 hour) build.
However, that was more of an exception.
Generally, I think because so many things depend on core, Jenkins would do
a full or nearly full build, so we never ended up saving that much time.
Sorry my memory is not better and I can't offer more detail on this.
On Sun, Oct 15, 2017 at 10:49 PM, Peter Palaga <[hidden email]> wrote: