Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Date: Mon, 31 Oct 2016 20:18:58 +0000 (UTC)
From: "Michael Osipov (JIRA)" <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.13016691.1477938073000.136748.1477945138574@Atlassian.JIRA>
In-Reply-To: <JIRA.13016691.1477938073000@Atlassian.JIRA>
References: <JIRA.13016691.1477938073000@Atlassian.JIRA> <JIRA.13016691.1477938073579@arcas>
Subject: [jira] [Updated] (MINVOKER-209)  ITs fail (on Windows 10) when
 working directory contains space
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 31 Oct 2016 20:19:00 -0000


     [ https://issues.apache.org/jira/browse/MINVOKER-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated MINVOKER-209:
------------------------------------
    Summary:  ITs fail (on Windows 10) when working directory contains space  (was:  ITs fail (on W10) when working directory contains space ?)

>  ITs fail (on Windows 10) 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
>              Labels: test-fail, window
>
> 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)