maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abel Salgado Romero (JIRA)" <>
Subject [jira] [Commented] (MINVOKER-198) mavenOpts in does not accept parameters with spaces
Date Sat, 13 Feb 2016 19:35:18 GMT


Abel Salgado Romero commented on MINVOKER-198:

I've been doing some debugging and seems that the MAVEN_OPTS are properly captured (as seen
in the code) and passed to the DefaultInvoker without modifications.
Further debugging I get to the final command line call in org.codehaus.plexus.util.CommandLine:L670,
and again the environment variable shows that MAVEN_OPTS is correct....I am really confused

> mavenOpts in does not accept parameters with spaces
> ----------------------------------------------------------------------
>                 Key: MINVOKER-198
>                 URL:
>             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
>         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:
> 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

View raw message