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>
