[
https://issues.apache.org/jira/browse/MINVOKER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958573#comment-17958573
]
Olivier Lamy commented on MINVOKER-185:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-invoker-plugin#650|https://github.com/apache/maven-invoker-plugin/issues/650].
> Cannot run invoker ITs on Windows with Maven 3.3.1
> --------------------------------------------------
>
> Key: MINVOKER-185
> URL: https://issues.apache.org/jira/browse/MINVOKER-185
> Project: Maven Invoker Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 1.9
> Environment: Apache Maven 3.3.1
> (cab6659f9874fa96462afef40fcf6bc033d58c1c; 2015-03-13T20:10:27+00:00)
> Java version: 1.8.0_31, vendor: Oracle Corporation
> Default locale: en_GB, platform encoding: Cp1251
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
> Reporter: Sergei S. Ivanov
> Assignee: Robert Scholte
> Priority: Blocker
> Fix For: 1.10
>
>
> {{mvn.bat}} has been renamed to {{mvn.cmd}} in Maven 3.3.1, and that appears
> to have broken the assumption in {{maven-invoker-plugin}}. I am unable to run
> integration tests under the new version of Maven.
> {noformat}
> [INFO] Building: TEST-9\pom.xml
> [INFO] ..FAILED (0.0 s)
> [INFO] Maven invocation failed. Error configuring command-line. Reason:
> Maven executable not found at: C:\Java\apache-maven-3.3.1\bin\mvn.bat
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
