[ https://issues.apache.org/jira/browse/MINVOKER-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381403#comment-15381403 ]
Abel Salgado Romero commented on MINVOKER-198: ---------------------------------------------- Thanks a lot for your support and explanation. I just used mavenOpts because it was the only thing that made some sense to me looking in the example in the documentation (http://maven.apache.org/plugins/maven-invoker-plugin/run-mojo.html#invokerPropertiesFile). It is the only place where a -D option is passed and goals does not mention that you can add options. Extending the explanation for goals saying you can add parameters would be great. > mavenOpts in invoker.properties does not accept parameters with spaces > ---------------------------------------------------------------------- > > Key: MINVOKER-198 > URL: https://issues.apache.org/jira/browse/MINVOKER-198 > Project: Maven Invoker Plugin > Issue Type: Bug > Affects Versions: 2.0.0 > Environment: Maven 3.3.9 and 3.2.5. > Linux/Mac > Reporter: Abel Salgado Romero > Fix For: waiting-for-feedback > > Attachments: mac_output.txt > > > Seems that mavenOpts does some additional parsing and comand line arguments > with spaces are not read correctly. > This prevents writing tests that when run on console in a normal maven build > they work. > Here is an example of what I want to test: > https://github.com/abelsromero/asciidoctor-maven-plugin/blob/attributes_command/src/it/article-html-attributes/invoker.properties > If you see the "asciidoctor.attributes" is a chain with many internal > parameters and spaces. This works on console, but not in the test. > But the test fails with the message: > Error: Could not find or load main class source-highlighter=coderay" -- This message was sent by Atlassian JIRA (v6.3.4#6332)