This tool could be useful in tracking down methods whose switch
statements need to be updated when, say, you add a new enum value. In
general, this tool could be useful wherever you have undeclared
dependencies among files and components, which the compiler can't track.
Thanks,
-Rick
On 12/15/15 3:51 AM, Igor Wiese wrote:
That is the idea Bryan.
Let's suppose that you are reviewing a certain issue, or started to
work in a issue and changed any file. Our approach would recommend
other files prone to change together in this task because the files
changed in past issues with the same "context" (context here means
issues with same reporter, committer, similar number of lines of code
added, removed, modified, size of discussion, etc)
Now, the idea is provide a webservice "as a oracle" that developers
from apache could visit and obtain this information, but we are
thinking in the best way to concept the tool and implement it.
Many thanks for your comment :)
2015-12-15 2:05 GMT-02:00 Bryan Pendleton<[email protected]>:
As a developer the normal "way" to find files to change together to
complete an issue is based on our own experience, debugging or through
the documentation, right?
Yes, I agree that is the normal way.
Also through code review, running tests, and messages from the compiler.
Is your idea that, given a database of change history as you have
described it, some tool would be able to notice when the developer
makes a certain type of change, and then suggest other related
changes that are typically made at the same time?
I think that's a pretty interesting idea.
bryan
