Thanks Sergey!
--
View this message in context:
http://cxf.547215.n5.nabble.com/Feedback-of-my-Phd-work-in-CXF-project-tp5763765p5763790.html
Sent from the cxf-dev mailing list archive at Nabble.com.
Hi Christian. Thank you again. You gave me good insights and ideas.
In fact there is other researcher checking if there are relation between
direct and "not direct" connections between classes and comparing then with
code changes. We found that structural dependencies are not "good
predictors" to
Thanks Sergey. This could be a good "next Step". I will think about it :-)
And, how about the recommendations while you are performing changes? Do you
think that based in the accuracy that we reported would be good to use some
tool to help you in your tasks?
It is difficult to you find files to ch
Hi Christian. Thanks for answer.
Your first question is interesting. Usually this is the natural reason why
we changed two files. We are always expecting some kind of structural
connection between classes (eg implements, extends, instantiation, etc.).
However we found many cases (issues) with comm
Hi, CXF Community.
My name is Igor Wiese, phd Student from Brazil. I am investigating two
important questions: What makes two files change together? Can we predict
when they are going to co-change again?
I've tried to investigate this question on the CXF project. I've collected
data from issue
