You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[INFO] --- maven-help-plugin:3.4.0:evaluate (default-cli) @ surefire-its ---
[INFO] No artifact parameter specified, using 'org.apache.maven.surefire:surefire-its:jar:3.2.4-SNAPSHOT' as project.
[INFO] Enter the Maven expression i.e. ${project.groupId} or 0 to exit?:
${jacoco-it.agent}
[INFO]
"-javaagent:C:\\Users\\mosipov\\.m2\\repository\\org\\jacoco\\org.jacoco.agent\\0.8.8\\org.jacoco.agent-0.8.8-runtime.jar=destfile=D:\\Entwicklung\\Projekte\\Maven Surefire\\surefire-its\\target\\jacoco.exec,includes=**/failsafe/*:**/failsafe/**/*:**/surefire/*:**/surefire/**/*,excludes=**/HelpMojo.class:**/shadefire/**/*:org/jacoco/**/*:com/vladium/emma/rt/*"
Expected behaviour
cmd.exe does not require bashslashes to be escaped. I have extracted the code from Maven Surefire:
Steps to reproduce
Have a look at this config snippet in Maven Surefire: https://github.com/apache/maven-surefire/blob/83c466698f1cf38d7b60852549393f4245f286d4/surefire-its/pom.xml#L136-L156
It produces the following output:
Expected behaviour
cmd.exe
does not require bashslashes to be escaped. I have extracted the code from Maven Surefire:Output:
The underlying implementation for calling the command is in Maven Shared Utils and will handle this w/o the double escaping.
Actual behaviour
Backslashes are uselessly escaped because
CommandLineSupport
does not differentiate between Bourne Shell input andcmd.exe
.This was foundw hile working on https://issues.apache.org/jira/browse/SUREFIRE-1810 and reported as https://issues.apache.org/jira/browse/SUREFIRE-2225.
Luckily both
File
andPath
normalize two backslashes to one...The text was updated successfully, but these errors were encountered: