Duansg opened a new pull request, #6436:
URL: https://github.com/apache/shenyu/pull/6436
### What
On the Windows leg of the `ci` workflow, build with `./mvnw.cmd` instead of
`mvnd`. mvnd is no longer installed or run on Windows; Linux legs are unchanged.
### Why
After #6435 merged, `build (17, windows-latest)` failed in "Build with
Maven":
```java
java.nio.charset.MalformedInputException: Input length = 1
at org.mvndaemon.mvnd.client.DaemonDiagnostics.tail(...)
```
The mvnd daemon (mvnd 1.0.2 / bundled JDK 22) dies mid-build; the client
then reads a non-UTF-8 daemon log with the platform charset and throws, masking
the real error. It reproduces reliably on Windows (non-UTF-8 default charset)
while Linux passes, and the `mvnd --version` guard can't catch it since the
daemon dies during the build, not at startup. Skipping mvnd on Windows removes
the path.
Not caused by #6435 — that PR only refactored paths-filter and touched no
build command. Pre-existing Windows/mvnd flake.
- [x] You have read the [contribution
guidelines](https://shenyu.apache.org/community/contributor-guide).
- [ ] You submit test cases (unit or integration tests) that back your
changes.
- [ ] Your local test passed `./mvnw clean install
-Dmaven.javadoc.skip=true`.
--
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]
