[
https://issues.apache.org/jira/browse/MNG-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-5792.
-------------------------------
Resolution: Not A Problem
As Karl Heinz layed out, use a newer version of MINVOKER.
> mvn.bat renamed to mvn.cmd -> maven-invoker-plugin:run fails
> ------------------------------------------------------------
>
> Key: MNG-5792
> URL: https://issues.apache.org/jira/browse/MNG-5792
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build
> Affects Versions: 3.3.1
> Environment: Windows 7 64 bit, Java 7
> Reporter: Jan Sievers
>
> steps to reproduce:
> # git clone https://github.com/takari/maven-polyglot.git
> # using maven 3.3.1 on WIndows, do a
> {code}
> mvn clean install
> {code}
> build fails with
> {code}
> [INFO] --- maven-invoker-plugin:1.5:run (integration-test) @ polyglot-ruby ---
> [INFO] Building: ruby_execute\pom.xml
> [INFO] ..FAILED (0.0 s)
> [INFO] Maven invocation failed. Error configuring command-line. Reason:
> Maven executable not found at: C:\tools\apache
> -maven-3.3.1\bin\mvn.bat
> [INFO] Building: use_jruby_installation\pom.xml
> [INFO] ..FAILED (0.0 s)
> [INFO] Maven invocation failed. Error configuring command-line. Reason:
> Maven executable not found at: C:\tools\apache
> -maven-3.3.1\bin\mvn.bat
> [INFO] -------------------------------------------------
> [INFO] Build Summary:
> [INFO] Passed: 0, Failed: 2, Errors: 0, Skipped: 0
> [INFO] -------------------------------------------------
> {code}
> it seems that mvn.bat was renamed to mvn.cmd with maven 3.3.1
> While maven-invoker-plugin could arguably be smarter to locate the mvn
> script, I think it's best to revert the rename unless there was a specific
> reason to rename from .bat to .cmd.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
