Re: [VOTE] Maven incremental build for BIG-sized projects with local and remote caching

2019-09-18 Thread Alexander Ashitkin
Sorry if duplicated, looks like my yesterday reply didn't come through. Sharing results. Configuration: * verify -T4 -P default,all-shapshots-repos * my project config (might be suboptimal for wicket) * scala tests disabled in 2 modules (caused bytecode version conflict on my machine) Results

Re: [VOTE] Maven incremental build for BIG-sized projects with local and remote caching [I]

2019-09-18 Thread Tibor Digana
I was the person who talked with Robert and Herve about incremental build in ASF Conference Budapest in 2015. I had an idea with a Java agent and optimize the test-set in Surefire but we all understood that a generic solution is not possible with full guarantees for all users which may finally brea

RE: [VOTE] Maven incremental build for BIG-sized projects with local and remote caching [I]

2019-09-18 Thread Falko Modler
Hi Maximilian, > 2. No IDE integration IDEs usually have their own mechanisms to build incrementally. They also execute Maven core in their own special way, often very different from the default command line execution. > 3. Further advanced optimizations don't look possible Feature requests a

Re: [VOTE] Maven incremental build for BIG-sized projects with local and remote caching [I]

2019-09-18 Thread Romain Manni-Bucau
(just cause I think it was not mentionned in this thread whereas it is very relevant) Here are some links converging with the overall idea: - https://cwiki.apache.org/confluence/display/MAVEN/Incremental+Builds?focusedCommentId=30149618 - http://maven.40175.n5.nabble.com/Re-parallelise-not-overla

RE: [VOTE] Maven incremental build for BIG-sized projects with local and remote caching [I]

2019-09-18 Thread Maximilian Novikov
Classification: For internal use only Hi Falko, I saw this project. It can help in some cases, but to build fast you need: 1. Incremental build 2. Remote cache(shared cache) gitflow-incremental-builder helps to cover #1. BTW I still see limitations here: 1. It creates coupling with GIT 2