Re: How Maven solves the problem of long builds on large projects?

Am Mon, 21 Dec 2015 21:23:56 +0100 schrieb Mirko Friedenhagen : > Hello Sergey, > > you may try to use > https://github.com/timgifford/maven-buildtime-extension to identify > which plugins contribute most to your long build times. I typically enable the timestamps in maven-home/conf/logging/sim

Re: How Maven solves the problem of long builds on large projects?

Hello Sergey, you may try to use https://github.com/timgifford/maven-buildtime-extension to identify which plugins contribute most to your long build times. Regards Mirko Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhage

Re: How Maven solves the problem of long builds on large projects?

Hi, we had a similar problem with our build. First step was to optimize our tests. By tracing the execution time of our tests we were able to reduce the time spent on integration tests from 1h to 15m. We use Team City as CI server. Therefore we were able to parallelize our build. How we run

Re: How Maven solves the problem of long builds on large projects?

Ideas: - Break your project up into modules that build separately. If you have a well structured project that is loosely coupled, individual issues/bugs will only affect a few modules. We have a project with about 80 modules but never build them all at once. - Build separately deployable modul

Re: How Maven solves the problem of long builds on large projects?

I doubt it is the compilation that sucks up the time. Try running with test execution skipped to see the time difference, eg `mvn clean install` vs `mvn clean install -DskipTests` If you are using `install` then likely there is no need to rebuild everything each time and you can use the -pl -am an

Re: How Maven solves the problem of long builds on large projects?

Hi, On 12/21/15 1:53 PM, Sergey Saraev wrote: Hello! I am developing a project with 67 modules. I use Apache Maven 3.0.4. Reassembly of the project take 1 hour and 50 minutes although usually commit change only one module. You should use only: mvn clean install ... any other things like pm

Re: How Maven solves the problem of long builds on large projects?

On 21 Dec 2015, at 12:53, Sergey Saraev wrote: > I am developing a project with 67 modules. > I use Apache Maven 3.0.4. > > Reassembly of the project take 1 hour and 50 minutes although usually commit > change only one module. > > The project is very large. It contains 5948 java classes (Basic

How Maven solves the problem of long builds on large projects?

Hello! I am developing a project with 67 modules. I use Apache Maven 3.0.4. Reassembly of the project take 1 hour and 50 minutes although usually commit change only one module. The project is very large. It contains 5948 java classes (Basically, time spent on their compilation.). Build command