| << Back to previous view |
|
[QB-3058] Maven Executable Name on Windows
|
|
| Status: | Closed |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | J. Mash | Assigned To: | Robin Shen |
| Resolution: | Won't Fix | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
It appears that the Maven plugin is not currently compatible with Maven when it is installed using the Chocolatey / Nuget package managers. The reason for this is that the package managers will generate a shim executable (mvn.exe) that points at the installed version of Maven, and it does not appear that the Maven plugin recognizes this.
Recent versions of Windows support a framework for package managers (https://www.howtogeek.com/200334/windows-10-includes-a-linux-style-package-manager-named-oneget/) for installing software in a manner similar to that of apt-get/yum on Linux. This framework allows Chocolatey / Nuget to be easily used as the backend repositories, so this seems like something that will be seeing more widespread use in the coming months (especially in configuration management scripts when setting up new hosts) |
| Comments |
| Comment by Robin Shen [ 18/Jan/18 07:50 AM ] |
| Can you please show me the command you used to install maven package with chocolate/nuget? Looks like I can not find the package "maven" with nuget |
| Comment by J. Mash [ 18/Jan/18 03:40 PM ] |
|
Here's what we have in our runbook:
- choco install maven I confirmed that this command still seems to work as well: Chocolatey v0.10.8 Installing the following packages: maven By installing you accept licenses for the packages. maven v3.5.2 already installed. Use --force to reinstall, specify a version to install, or try upgrade. Chocolatey installed 0/1 packages. See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log). Let me know if there's any additional information I can provide to help with this. |
| Comment by Robin Shen [ 19/Jan/18 12:56 AM ] |
| Thanks for the info. I tried it and the mvn.cmd needs to be specified as maven executable. |