Failure to build

[taxuexunshang]

Describe the bug
I tried to build spring security source code from the main branch of github. An error was then generated during the build phase. The error log is as follows:

What went wrong:
Execution failed for task ':spring-security-config:rncToXsd'.
javax.xml.transform.TransformerConfigurationException: Failed to compile stylesheet. 1 error detected.

Try:
Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Get more help at https://help.gradle.org.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.7/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD FAILED in 3m 32s
8 actionable tasks: 7 executed, 1 from cache

My Java version is "17.0.11" 2024-04-16 LTS.

To Reproduce
Clone the source code from the main branch of github. and then execute gradlew publishToMavenLocal or gradlew build.

I look forward to your help. Thank you!

[taxuexunshang]

Detailed exception information is here

Error
java.net.MalformedURLException: no protocol:
/workspace/spring-security/config/src/main/resources/org/springframework/security/config/spring-security.xsl

[jzheaux]

Hi, @taxuexunshang, thanks for reaching out! Sorry you are having trouble.

The build appears to be working fine for me and for our CI. It might have been a blip. If you are still seeing the error, will you please share your operating system?

[spring-projects-issues]

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

[spring-projects-issues]

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.