[
https://issues.apache.org/jira/browse/MINVOKER-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte reopened MINVOKER-209:
-------------------------------------
Reopening, IT 'special-characters-should-work' is still failing on my system.
Traced it back to r1763932 where the test was adjusted with extra spaces.
{noformat}
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T17:41:47+01:00)
Maven home: d:\apache-maven-3.3.9\bin\..
Java version: 1.7.0_55, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_55\jre
Default locale: nl_NL, platform encoding: Cp1252
OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"
{noformat}
> 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
> Assignee: Michael Osipov
> Priority: Minor
> Labels: test-fail, window
> Fix For: 3.0.0
>
> Attachments:
> MINVOKER-209-maven-invoker-plugin-IT-double-exec-special-characters-should-work.patch,
> MINVOKER-209-workaround-maven-invoker-plugin.patch
>
>
> 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)
