Well maven still has to go through all the lifecycle, which involves generating resources, compiling, packaging, running tests, checking snapshots, etc. So depending on your plugin, repository configuration you could get faster/slower subsequent builds. Unlike gradle, maven doesn't cache steps so the slowness is mostly due to having to go through the lifecycle.
As far as I remember, the mailing list mentioned the takari lifecycle which changes a bit how maven works. You might want to experiment with it. http://takari.io/book/40-lifecycle.html On Thu, Apr 6, 2023, 18:15 Tommy Svensson <to...@natusoft.se> wrote: > Hello maven users, > > I have an observation that does not make sense to me: > > I have a multi module build of about 5 modules. > > I do an "mvn clean install" and it takes 43 seconds. > > I then do an "mvn install" and it takes 43 seconds ! > > The second time everything was already built, so no compilation at all > should have been done. So why does it still take 43 seconds ? I can do "mvn > install" over and over again and it takes 43 seconds. No diff between "mvn > clean install" and "mvn install" when everything is already built. > > Is the compile so extremely fast that it doesn't even take a second while > everything else maven does takes 43 seconds ? > > I have a Mac M1 with 10 cores and 64 GB of memory (and no buss, processor > and memory in same chip). The maven speed difference between my machine and > the work machine (Intel I5 2 cores and 8GB memory) doesn't really differ > that much. That is with maven. For other things there is a big difference. > > Is there any good explanation for this ? I have used maven for a very long > time and this is the first time I have noticed this. New faster machines > have always improved build speed before. > > I'm running Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0) > That is what the latest version of IDEA gives me. > > > BR, > Tommy Svensson > > > >
