Is what you want different from what mvn -amd moduleA
does? So your idea is to find the list of changed modules and then build that list with -amd? thanks david jencks On Aug 25, 2012, at 1:32 PM, Mark Struberg wrote: > Hi folks! > > After a short discussion with Kristian, I've created a small app with 2 > modules which shows a few problems with mavens incremental build logic. > And since incremental builds do not work well, people use > > $> mvn _clean_ install > all the time. > > We could speed up the development effort heavily if we make > $> mvn install > (without an upfront clean) more reliable. > > > The sample [1] consists of moduleA and moduleB with BeanA and BeanB > respectively. > BeanB has a private BeanA field and moduleB has a dependency on moduleA. > > If I change BeanA and just invoke mvn install then only moduleA gets rebuilt. > We currently do not rebuild moduleB, but we should do to create a reliable > output. > > In fact, the incremental build within a single module already works to some > degrees, but we must detect a change in dependencies and trigger a full > rebuild on all depending modules. This could be done by storing the md5 of > all dependency artifacts and compare them on the next build. If the md5 of a > dependency did change, then we need to build the module full cycle. > Other ideas are welcome. Slaps as well if I forgot some obvious stuff and all > works well already. > > > LieGrue, > strub > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
