yeah basically its always there you cant get rid o...

# announcements

[vach]

yeah basically its always there you cant get rid of it, but if you have no .java files it almost doesnt take time... makes sense

[Mike]

I believe IntelliJ now supports delegating build/test to maven now BUT I doubt that will do what you want, as IntelliJ has no idea what has been done, and what hasn’t. It just ‘blindly’ calls maven targets. And maven will re-do things as it doesn’t track.

This is one area where Gradle works better as Gradle is much better about knowing what’s up-to-date and what isn’t.

So if you call build from the CLI twice, the second time, nothing should get done, just all the tasks showing as ‘up-to-date’.

[vach]

Yeah i just tried this, it delegates "mvn install" every time. This sucks.
maven perfectly reuses compilation as well, my problem is that intellij recompiles almost everything all the time. Gradle is way slower than maven i dont know what crap did they do over the years but it sucks, i changed it for maven.

[Mike]

Maven delegation support in IntelliJ is quite new, so I’d suggest you move to an IntelliJ forum, discuss there, and raise tickets.

As to Gradle being slow, well, I won’t get into that ‘discussion’ 😉

[vach]

Yeah i used to open tickets, for few years then i got sick of it, and realized i can run a mvn package + write a simple 30 line kotlin script that does all the build customizations i need and voila, i have around few second builds instead of gradles few minute builds...

My only problem is once i let maven do anything intellij has to recompile a bunch of stuff and index which takes substantially more than the build itself...