Everything fine with the usual projects.
There is a typo in the release notes:
Now, with your help and guidance we’ve been able to made a couple of highly-requested code-quality plugins improvements:
should say “able to make”.
It would be helpful if the Incremental Java compilation documentation would include some sample code showing how to easily enable it for all modules applying the java plugin instead of just linking to the JavaCompile docs. One less hurdle preventing users from trying out the new feature.
I raised issue #8120 over at spring-boot regarding deprecation warnings.
This isn’t 3.4-rc-1 related but it would be nice if you could take a look at the Having the ability to see what triggered dependency resolution topic and give me some feedback about whether or not my assumption is correct.
The thing is that our huge (or “bigly” in newspeak) in-house project takes about one minute of configuration time and it’s getting worse with every additional spring-boot application.
I guess we are not the only ones suffering from this spring-boot-gradle-plugin problem and assume that most people simply think that the slow startup is Gradles fault. You could probably sort this out with the Spring folks directly.