arturobernalg opened a new pull request, #13947:
URL: https://github.com/apache/maven/pull/13947
readCoreExtensionsDescriptor() let any failure from the XML parser escape
as-is, so an empty or otherwise malformed .mvn/extensions.xml surfaced as a
bare "input contained no data" EOFException with a full stack trace instead of
a message naming the problem file.
Wrap the parse failure in an IOException that names the extensions file,
keeping the original exception as the cause so -e still shows the full chain.
Fixes #10258
Also reproduces on maven-3.9.9/3.9.x via the equivalent code in
maven-embedder's MavenCli (same unguarded parser.read() call, different file
API). Happy to open a backport PR to maven-3.9.x if a maintainer wants it there
too.
<!--
Please open pull requests against one of the following branches:
- master — default target for all changes (new features + bug fixes).
If the change should also go to maven-4.0.x, request a backport in the PR.
- maven-3.10.x — target for 3.x changes (new features + bug fixes).
If the change should also go to maven-3.9.x, request a backport in the PR.
maven-3.9.x should receive only serious bug fixes, as it is approaching
EOL.
Backports are typically handled by maintainers;
however, after agreement you may open a separate backport PR to the target
maintenance branch.
-->
<!-- Add your description here... what, why and how you resolve the issue -->
---
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](https://www.apache.org/licenses/LICENSE-2.0)
check one of the following:
- [x] I hereby declare this contribution to be licensed under the [Apache
License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0)
- [x] I hereby declare that I have filed 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]