See gh-22387

See gh-22386

See gh-22385

See gh-22384

See gh-22383

See gh-22382

See gh-22376

See gh-22375

See gh-22374

See gh-22372

See gh-22371

See gh-22370

Closes gh-22359

* pr/22296:
  Polish "Restructure "Building Container Images" section"
  Restructure "Building Container Images" section

Closes gh-22296

See gh-22296

See gh-22296

* pr/22344:
  Handle null items as advertized in the Javadoc

Closes gh-22344

See gh-22344

Closes gh-22345

Closes gh-22347

Closes gh-22348

Closes gh-22351

Fixes gh-22350

This commit adds a check to the support code for the Gradle plugin
bootBuildImage task to ensure that the jar file that will be passed
to a builder is readable and has a valid directory. This prevents a
situation where the jar file cannot be read because it is prepended
with a launch script, and the builder does not receive any files to
process.

Notes have also been added to the Gradle plugin documentation to warn
against using a bootJar launchScript configuration and bootBuildImage
together, as well as caveats about launchScript that match the Maven
plugin documentation.

Fixes gh-22223

Closes gh-22339

Closes gh-22337

* pr/22330:
  Avoid unnecessary allocations in ConditionMessage for NORMAL style

Closes gh-22330

See gh-22330

* gh-22112:
  Cleanup temporary files after Maven plugin execution

Closes gh-22112

See gh-22112

* gh-22294:
  Reduce started threads in OnClassCondition

Closes gh-22294

Prior to this commit, OnClassCondition started a thread even if the number of
passed autoconfiguration class candidates never exceeded 1. This commit only
starts a thread if there is actually work to split in half.

See gh-22294

Closes gh-22325

Previously, regular bean definitions for configuration properties classes
that attempt to use constructor binding were detected in a bean factory
post-processor, ConfigurationPropertiesBeanDefinitionValidator. This
validation examined every standard bean definition and failed if it
encountered one for a class that should have used constructor binding.
There were two downsides to this approach:

1. Reflection used to identify if the bean should be using constructor
   binding triggered class loading that could prevent subsequent
   instrumentation by a load-time weaver.
2. The cost of the validation was incurred when there was no
   misconfiguration to report.

This commit replaces ConfigurationPropertiesBeanDefinitionValidator
with a failure analyzer. This failure analyzer only runs once a failure
has occurred and the application context is not going to complete
refresh. This avoids causing problems with subsequent instrumentation
and also avoids the cost of validation and error reporting unless there
is an error.

Fixes gh-20798