tanvir-ux opened a new pull request, #447:
URL: https://github.com/apache/maven-wrapper/pull/447

   When the extracted archive directory name does not match the archive 
filename, both wrapper scripts scan for a subdirectory that contains 
`bin/$MVN_CMD`. Unix `only-mvnw` already stops at the first match. 
`only-mvnw.cmd` used `ForEach-Object` with no early exit, so the last match won.
   
   I changed the Windows scan to a `foreach` with `break` so both scripts pick 
the same directory from the same archive.
   
   Fixes #442
   
   Following this checklist to help us incorporate your
   contribution quickly and easily:
   
   - [x] Your pull request should address just one issue, without pulling in 
other changes.
   - [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   - [x] Each commit in the pull request should have a meaningful subject line 
and body.
     Note that commits might be squashed by a maintainer on merge.
   - [ ] Write unit tests that match behavioral changes, where the tests fail 
if the changes to the runtime are not applied.
     This may not always be possible but is a best-practice.
   - [ ] Run `mvn verify` to make sure basic checks pass.
     A more thorough check will be performed on your pull request automatically.
   - [ ] You have run the integration tests successfully (`mvn -Prun-its 
verify`).
   
   This is a few-line script change in `only-mvnw.cmd`. I did not add a 
PowerShell test harness.
   
   - [x] I hereby declare this contribution to be licenced under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   - [ ] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to