Error messages that were eaten somewhere near exec-maven-plugin> Node.js> r.js

We use exec-maven-plugin to run the RequireJS optimizer (r.js) in Node.js (because it is much faster than Rhino):

<plugin>
    <groupId>org.codehaus.mojo</groupId>
    <artifactId>exec-maven-plugin</artifactId>
    <version>1.2</version>
    <executions>
        <execution>
            <id>compile-js</id>
            <phase>prepare-package</phase>
            <goals>
                <goal>exec</goal>
            </goals>
            <configuration>
                <executable>${node.executable}</executable>
                <arguments>
                    <argument>${project.build.directory}/dependency/requirejs/r.js</argument>
                    <argument>-o</argument>
                </arguments>
            </configuration>
        </execution>
    </executions>
</plugin>

The problem is that whenever there is any problem during compilation, the error messages that r.js is supposed to cause do not appear on the output of the Maven console. What I'm doing to troubleshoot, I will rerun the Maven command with the -X flag to get debug output so that exec-maven-plugin prints the current executable command. This is something like:

project-root / target / dependency / node / node \
    project-root / target / dependency / requirejs / r.js \
    -o src / main / webapp / app.build.json

, , .

stderr stdout 2>&1 ( Windows), exec-maven-plugin . , , stderr/stdout - , .

, , , ? , : Maven, exec-maven-plugin, Node.js, r.js .

P.S. requirejs-maven-plugin , POM . , - .