Aggregated Javadoc no longer published since 7.0.0-M4

[bclozel]

This is a regression that was introduced in #27497.

Although we compile sources with a Java 24 toolchain (targeting Java 17 bytecode), we are still using Java 17 to run the Gradle build.

[sbrannen]

In commit 49ef150, I stated that the common javadoc task used by all spring-* modules would be addressed in a separate commit. However, after further investigation I determined that the spring-test Javadoc JAR was published successfully, including links to JUnit 5 Javadoc (which was not previously the case).

• https://repo1.maven.org/maven2/org/springframework/spring-test/7.0.0-M4/spring-test-7.0.0-M4-javadoc.jar

The reason is that the javadoc task automatically uses the toolchain configured by our JavaConventions plugin for each spring-* project.

So, it was just the aggregated Javadoc in the framework-api project that did not get generated/published for 7.0.0-M4, and commit 49ef150 already ensures that the javadoc task for the framework-api project has its toolchain set to Java 24 like JavaConventions does.