René Just

@jose Is this something that should be tracked on the GZoltar side?

Make sure that subversion is installed and its svn executable is on the PATH. You can run `svn --version` from the command-line to check whether svn is available.

Hi @jmueducn, We are in the process of changing the test command to directly invoke the JUnit5 console launcher under the hood. This will allow you to run `defects4j test...

Hi @jmueducn, Thanks for reporting this. Unfortunately, I cannot reproduce the issue. Can you please let me know: * are you using the most recent version of Defects4J? * what...

@universetraveller are you willing to send a PR with a more robust test-replacement approach?

Hi @jmueducn, All patches for the projects in Defects4J are written by the project maintainers themselves. It is possible that some patches do not, or only partially, fix the root...

Hi @lemon1-ui, You can use the query command to obtain that information. For example: ``` defects4j query -p Lang -q "report.id,report.url" ``` (`defects4j query -p Lang -H`) will list all...

Hi @2ira, I think what you are looking for is the configuration [here](https://github.com/rjust/defects4j/blob/master/framework/projects/defects4j.build.xml#L222). If you add relevant export options to the build target, then Major will export the source-code mutants...

@Hoyeon9, do you have a concrete use case where this behavior is a problem and a concrete proposal for how to address it?

Hi @lemon1-ui, Currently, there is no Defects4J command that provides this information. You can use a source-code or byte-code analysis to map patched lines to method names, including (generated) constructors...