Keep in mind that the reactor in general resolves the jar within the multi-module project... so you don't know which source files changed as easily and therefore you don't know which .class files to remove
If you run with -DskipTests most builds are very fast anyway (hey I regularly rebuild all of Jenkins clean every day) and any decent unix guy worth their crusties should be able to fork maven in the background to build for them ;-) On 4 July 2012 15:30, Dmitry Trunikov <[email protected]> wrote: > > The way I do this is to use my IDE's dependency analysis to have my IDE > do a "Make" (which rebuilds all the downstream changes)... then before I > commit I will do a "mvn clean verify" to make sure that my changes are good > > > Yes my IDE does the analysis too. > The problem is in my colleague. > He is unix geek and orthodox and use Emacs as java IDE. At the start of > the project we had a long discussion what use as build tool. > He insisted on Ant because he knew exactly how it works and can easily > adjust build process. > I proposed to use Maven as it has perfect support of multi-module projects > (at least I thought so at that time). > I frustrated a lot because in my opinion recompilation of dependent > modules when dependency was changed is a main goal of any matured build > tool. > And I was convinced that Maven reactor mechanism does it perfectly. > Actually I can't believe in absence of such functionality in Maven. >
