You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gili (JIRA)" <ji...@apache.org> on 2018/07/06 03:12:00 UTC

[jira] [Comment Edited] (MNG-6385) Windows mvn.cmd fail with incorrect command syntax.

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

Gili edited comment on MNG-6385 at 7/6/18 3:11 AM:
---------------------------------------------------

So, hmm, two questions come to mind:

1. Why did this work in 3.3.9? Meaning, what changed between 3.3.9 and 3.5.2 that all of a sudden command-line parsing is broken?
2. I know this might sound blasphemous and all but... if we can't find a way to make this work using batch files, why not use a native binary instead? That is pretty much guaranteed to work without jumping through all these hoops.
3. Even easier: wrap a dumb batch file around a Java launcher that does more of the heavy-lifting.


was (Author: cowwoc):
So, hmm, two questions come to mind:

1. Why did this work in 3.3.9? Meaning, what changed between 3.3.9 and 3.5.2 that all of a sudden command-line parsing is broken?
2. I know this might sound blasphemous and all but... if we can't find a way to make this work using batch files, why not use a native binary instead? That is pretty much guaranteed to work without jumping through all these hoops.

> Windows mvn.cmd fail with incorrect command syntax.
> ---------------------------------------------------
>
>                 Key: MNG-6385
>                 URL: https://issues.apache.org/jira/browse/MNG-6385
>             Project: Maven
>          Issue Type: Bug
>          Components: Command Line
>    Affects Versions: 3.5.0, 3.5.2, 3.5.3
>            Reporter: Eric Barboni
>            Priority: Major
>
> Hi, during some test using Apache Netbeans on windows it appears that some cli can lead to failure of executing mvn.cmd
> It was working before on 3.3.9 version.
> In the code example (below) if space are removed from path in agentpath section it works.
> Otherwise the arguments are cut during evaluation
> and the following syntax incorrect will happen
> if not "-agentpath:\"E:\opensource\space" == "" (
> Best Regards
> {code}
> e:\outils\apache-maven-3.5.3\bin\mvn -Dexec.args="-agentpath:\"E:\opensource\space netbeans\netbeans\profiler\lib\deployed\jdk16\windows-amd64\profilerinterface.dll\"=\"E:\opensource\space netbeans\netbeans\profiler\lib\",5140,10 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=C:\Users\barboni\AppData\Local\NetBeans\Cache\dev\mavencachedirs\2080072884\org-netbeans-modules-profiler  -classpath %classpath com.mycompany.mavenproject23.newClass"  -Dexec.executable="C:\Program Files\Java\jdk1.8.0_162\bin\java.exe" -Dexec.classpathScope=runtime -DskipTests=true -Dmaven.ext.class.path="E:\opensource\space netbeans\netbeans\java\maven-nblib\netbeans-eventspy.jar" -Dfile.encoding=UTF-8 org.codehaus.mojo:exec-maven-plugin:1.5.0:exec
> {code}



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