Hi, You can't do that with javac, but the takari-plugins maintain a fine grained dependency graph in order to do incremental builds.
With tests, it is a different thing, though. Their runtime behaviour may depend on more than their class dependency might tell you: property/xml files, dependency injection - stuff like that. I think clover (code coverage tool for test) has a feature to run only tests for which any code has changed that has been recorded to be used in the previous run. So for real incremental tests out of the box, we'd have to support different strategies: compile-time dependencies, resource dependencies, runtime dependencies. That's quite an undertaking. For Surefire 3 we want to open up the API to allow attaching stuff like that from the outside. Andreas Am Mittwoch, 11. Februar 2015 schrieb Kevin Burton : > Is there an easy way to build the Java dependency tree from the compiler? > > I was thinking that if you can get the Java dependency tree built, then you > take take a look at a diff and look at which files have changed. > > Then from there you could take say 1000 test and reduce that to only 10 > test if only those ten had their dependencies changed. > > The theory being that if the previous commit already tested the previous > 990, why test them again? > > The epiphany I had was that one could EASILY integrate this into maven by > just passing a list of which tests to skip. > > This could dramatically improve the speed of continuous integration systems > > -- > > Founder/CEO Spinn3r.com > Location: *San Francisco, CA* > blog: http://burtonator.wordpress.com > … or check out my Google+ profile > <https://plus.google.com/102718274791889610666/posts> > <http://spinn3r.com> >
