maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alix Lourme (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MINVOKER-209) ITs fail (on W10) when working directory contains space ?
Date Mon, 31 Oct 2016 18:21:58 GMT
Alix Lourme created MINVOKER-209:
------------------------------------

             Summary:  ITs fail (on W10) when working directory contains space ?
                 Key: MINVOKER-209
                 URL: https://issues.apache.org/jira/browse/MINVOKER-209
             Project: Maven Invoker Plugin
          Issue Type: Test
    Affects Versions: 3.0.0
         Environment: Windows 10
            Reporter: Alix Lourme
            Priority: Minor


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

h3. Scenario

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

h4. working directory with spaces

_build.log_ result : 
{code}
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
{code}

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

cmd:
{code}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"
{code}

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

h3. working directory without space

_build.log_ result:
{code}
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
{code}

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

cmd:
{code}
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"
{code}

workDir:
{code}
C:\Windows\Temp\maven-invoker-plugin\target\it\special-characters-should-work
{code}

I'm not sure of the root cause (invoker initialization or _plexus-utils_ problem :()



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message