[MINVOKER-209] ITs fail (on Windows 10) when working directory contains space

• Type: Test
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.0.0
• Labels: test-fail window
• Environment: Windows 10
• Assignee: Michael Osipov
• Reporter: Alix Lourme
• Created: 31/Oct/16 18:21
• Updated: 23/Apr/18 08:14
• Resolved: 17/Jan/17 11:29

Description

When working copy contains some space (common situation on W10 with users directories Firstname/Lastname), most of ITs fail.

Scenario

Command:

mvn invoker:run -Dinvoker.test=special-characters-should-work -Dfile.encoding=UTF-8 -Prun-its,dev

working directory with spaces

build.log result :

Running pre-build script: C:\Users\Firstname Lastname\git\maven-plugins\maven-invoker-plugin\target\it\special-characters-should-work\setup.groovy
Finished pre-build script: C:\Users\Firstname Lastname\git\maven-plugins\maven-invoker-plugin\target\it\special-characters-should-work\setup.groovy
Erreur : impossible de trouver ou charger la classe principale Lastname\git\maven-plugins\maven-invoker-plugin\target

Content of : DefaultInvoker.executeCommandLine(Commandline, InvocationRequest) (line: ~126)

cmd:

cmd.exe /X /C ""C:\Program Files\[MavenDirectory]\bin\mvn.cmd" -B -X -D "maven.repo.local=C:\Users\Firstname Lastname\git\maven-plugins\maven-invoker-plugin\target\local-repo" -s "C:\Users\Firstname Lastname\git\maven-plugins\maven-invoker-plugin\target\it\interpolated-settings.xml" -D maven.compiler.source=1.6 -D maven.compiler.target=1.6 clean verify"

workDir:

C:\Users\Firstname Lastname\git\maven-plugins\maven-invoker-plugin\target\it\special-characters-should-work

working directory without space

build.log result:

Running pre-build script: c:\Windows\Temp\maven-invoker-plugin\target\it\special-characters-should-work\setup.groovy
Finished pre-build script: c:\Windows\Temp\maven-invoker-plugin\target\it\special-characters-should-work\setup.groovy
Apache Maven 3.4.0-SNAPSHOT (54827e6b0fc02425f701cfcccde46f81edcb7058; 2016-10-01T18:01:52+02:00)
... next lines are ok : BUILD SUCCESS

Content of : DefaultInvoker.executeCommandLine(Commandline, InvocationRequest) (line: ~126)

cmd:

cmd.exe /X /C ""C:\Program Files\[MavenDirectory]\bin\mvn.cmd" -B -X -D maven.repo.local=C:\Windows\Temp\maven-invoker-plugin\target\local-repo -s C:\Windows\Temp\maven-invoker-plugin\target\it\interpolated-settings.xml -D maven.compiler.source=1.6 -D maven.compiler.target=1.6 clean verify"

workDir:

C:\Windows\Temp\maven-invoker-plugin\target\it\special-characters-should-work

I'm not sure of the root cause (invoker initialization or plexus-utils problem )

Issue Links

• depends upon: MNG-5962 mvn.cmd fails when the current directory has spaces in between
• is blocked by: MNG-4559 MAVEN_OPTS are incorrectly resolved in Unix
• relates to: MINVOKER-211 Some ITs can't be re-executed without clean