defects4j icon indicating copy to clipboard operation
defects4j copied to clipboard

'defects4j' is not recognized as an internal or external command

Open Furqan1990 opened this issue 3 years ago • 4 comments

I need help with this problem "'defects4j' is not recognized as an internal or external command, operable program or batch file." I am trying to give Defects4J PATH but it's always giving me an error. I am using windows 10 operating system Capture

Furqan1990 avatar Jul 29 '21 08:07 Furqan1990

On Windows, you may need to call the defects4j command using perl <fullpath to defects4j>\defects4j.

rjust avatar Jul 30 '21 06:07 rjust

On Windows, you may need to call the defects4j command using perl <fullpath to defects4j>\defects4j.

Access Denied

Furqan1990 avatar Jul 30 '21 10:07 Furqan1990

@Furqan1990 have you been able to solve this issue on Windows?

rjust avatar Dec 31 '21 23:12 rjust

I don't think Defects4J will work on Windows cmd or PowerShell. There are Bash files and Bash commands in the code.

As long as you are in the Perl realm, some parts work. For example, The info command for projects and bugs works. But first, there is ./init.sh, and after that, you hit the Major framework's Bash files for compiling and testing projects. There are also some hardcoded Bash commands in the Perl code.

The easiest way to use Defects4J on Windows is through WSL. I think it's better to mention this in the README. The README says on Windows use perl "fullpath"\defects4j, and as a newcomer, you may assume by that instruction it will work on Windows.

h4iku avatar Apr 29 '22 07:04 h4iku