You are correct of course. There is a scala compiler plugin that allows you access to the entire dependency graph so if you have the changed files you can detect all the affected files. SBT does a great job of this. I was considering at some point doing this work (when it can fit into my schedule of course). I wanted to ensure that I will have the tools required for this.
On Thu, Apr 1, 2010 at 5:38 PM, John Murph <[email protected]> wrote: > I think you are basically correct. For the use case you are considering, > however, there are complications. You would not need to compile only the > changed file, but all dependent files. For instance, if the change was to > delete a method from a class, and another source file used that method it > would need to be recompiled (which might generate a compile error). > Handling compilation dependencies is something that Gradle wants to improve, > but it's a significant effort so it might be a while yet. > > Hope this helps, > -- > John Murph > Automated Logic Research Team >
