| << Back to previous view |
|
[QB-2813] Maven Executable Name Incorrect on Windows in Some Cases
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | J. Mash | Assigned To: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
Greetings,
I believe I have encountered a bug in the Maven plugin that prevents it from correctly determining the name of the Maven executable on Windows in some circumstances. Specifically, it seems to be hard-coded to use 'mvn.bat' as the Maven executable, and that was deprecated and removed in Maven 3.3.x. Here are my test cases: - Maven plugin settings define a 'Maven Home' setting: - With Maven v3.2.x, where the 'mvn.bat' exists, the 'mvn.bat' executable name is used. - With Maven v3.3.x, where the 'mvn.bat' does not exist, the 'mvn.cmd' executable name is used. - Maven plugin settings DO NOT define a 'Maven Home' setting: - With Maven v3.2.x, where the 'mvn.bat' exists, the 'mvn.bat' executable name is used. - With Maven v3.3.x, where the 'mvn.bat' does not exist, the 'mvn.bat' executable name still being used. Thanks, -J. Mash |