Major Changes Introduced
…have a problem getting the major classpath but that shouldnt be too much of an issue really
… getting the right results
…ning that I forgot about
@tomecho, overall this looks good. Can you please update the PR by pulling in the latest changes from master and by addressing the minor comments? Once all changes from master are pulled in, all bugs will be reproduced by travis, which would be a great sanity check.
…ownload-issues.pl script in the bug-mining framework requires two additional functions only available in recent versions: the 'all' function is available since version 1.33 and 'pairmap' function is available since 1.29.
… the modified files.
…d, but I allow them to be set, and have enabled the query option to actually work, as that is needed for projects like GSON that do not label issues as 'bug'
This means I get a "Unsupported build system" error, even though Gson is actually a Maven project - there's not a pom.xml file in the default work directory. I need to be able to point the script instead to
This same issue affects the functionality in the project file too. There, I can make it work by altering the project file to account for the directory shift. Of course, I could also do this in initialize-revisions.pl, but I wonder if we could support subprojects in a cleaner manner that does not require one-off edits to core bug mining files. Any thoughts?
Greg4cr left a comment
I have worked through the process with JacksonCore. I have only worked through a couple of the example bugs, but each stage of the bug mining process appears to work.
There are some compilation errors that prevent a full replication of the earlier process I followed. I'll look into those when I have more time. However, I suspect these are not a result of anything inherent to the bug mining process.
I think we can merge in the PR. After the holidays, I can give this a more extensive evaluation by working through the new projects.
…ects4j into merge-bug-mining-into-master