This fixes #19046 .

Signed-off-by: Nikolas Grottendieck [email protected]

Context

See #19046 for additional details.

There is one caveat with the current solution: if the XML parser encounters an error with the toolchains file, e.g. it's not valid XML, it'll print a message to stdout separate from any logging/exception handling in place: [Fatal Error] :1:1: Content is not allowed in prolog. for example. I have not found a way of turning that off :(.

Concerning the integTest checkbox … this doesn't exist for the jvm-services subproject?

Contributor Checklist

• Review Contribution Guidelines
• Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
• Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
• Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
• Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
• Provide unit tests (under <subproject>/src/test) to verify logic
• Update User Guide, DSL Reference, and Javadoc for public-facing changes
• Ensure that tests pass sanity check: ./gradlew sanityCheck
• Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Gradle Core Team Checklist

• Verify design and implementation
• Verify test coverage and CI build status
• Verify documentation
• Recognize contributor in release notes