[ 
https://issues.apache.org/jira/browse/MNG-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358453#comment-16358453
 ] 

Robert Scholte commented on MNG-6256:
-------------------------------------

{noformat}

set FILE_ARG=
:arg_loop
if "%~1" == "-f" (
 setx FILE_ARG="%~2"
 shift
 goto process_file_arg
)
if "%~1" == "--file" (
 setx FILE_ARG="%~2"
 shift
 goto process_file_arg
)

{noformat}

 

switching to {{setx}} seems to work. Not sure what the impact will be, so maybe 
better not do it for 3.5.x

> Maven script can break if "-f" path contains special characters 
> ----------------------------------------------------------------
>
>                 Key: MNG-6256
>                 URL: https://issues.apache.org/jira/browse/MNG-6256
>             Project: Maven
>          Issue Type: Bug
>          Components: Command Line
>    Affects Versions: 3.5.0
>         Environment: Windows 10 with PowerShell
>            Reporter: Christoph Etzel
>            Priority: Major
>             Fix For: 3.5.3-candidate
>
>
> Executing maven on Windows using the {{\-f}} or {{--file}} parameter to 
> specify an alternate POM file can break the script if the path contains 
> special characters. 
> It was originally discovered on a Windows Jenkins instance with working 
> directory located under C:\Program Files (x86)\Jenkins......
> Example:
> {code:java}mvn -f "folderWithClosing)Bracket/pomFolder"{code}
> Command line output: {{"Bracket/pomFolder" kann syntaktisch an dieser Stelle 
> nicht verarbeitet werden.}}
> Just for fun: Starting calc from maven script using {{\-f}}
> {code:java}mvn -f " ' & start calc"{code}
> Command line output: {{POM file  '}} and a new calculator process
> The bug was introduced with commit 
> https://github.com/apache/maven/commit/f8ab2a650f32d5d87126d341d9bbfccbf99fd0ca
>  for issue MNG-5889.
> Workaround: Use maven 3.3.9 or below
> Possible fix: Escape {{%FILE_ARG%}} and {{%POM_DIR%}} with {{"}} in {{echo}} 
> commands in {{maven.cmd}} (line 120 and 129).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to