René Just

@jose I was thinking about a submodule solution, but I agree it will be less convenient. As an alternative, having a snapshot of *all* pre-computed metadata in a dedicated repo...

@Greg4cr and @jose, for this particular PR, let's make a decision on what the semantics of the `-r` flag (test, coverage, etc.) should be for `b.orig` project versions and make...

This is related to issue #111. Defects4J calls the compile task of the project before exporting a property. Since the dependencies are set up in a way that every compilation...

Hi @markro49, Can you provide a bit more context? Are you referring to compiling the developer-written tests that come with the Closure subjects, or are you referring to automatically generated...

Hi @RollerKing, Seems like the mutation analysis ran out of memory. (Closure is a particularly resource-hungry project, and even running the tests without mutation can result in OOM issues.) Can...

Hi @neelofarhassan, Thanks for reporting this. The problem here is that the mutated class (`Entities.java`) is very large with many statements that can be mutated. Once Major generates and embeds...

I just merged this PR yesterday, so this is a very recent change. The documentation that you linked should be up to date; maybe you need to refresh. Let me...

Hi @gouxiaodong, The shared `all_classes.txt` file indeed includes a number of invalid entries (e.g., *org.apache.commons.lang3.ArrayUtils.add.T*); these should be removed. Perhaps this invalid output points to a bug in the used...

Thanks for reporting this, @islamelgendy. I was able to reproduce this and will look into the root cause. Best, René

Thanks for reporting this, @anjiperera! We will fix the exported classpath. As a workaround, it is safe to assume that the default version of junit (4.11) is sufficient to reproduce...