See gh-16317

See gh-16317

See gh-16316

* gh-16316:
  Polish "Use HTTPS for external links wherever possible"
  Use HTTPS for external links wherever possible

Closes gh-16316

See gh-16316

See gh-16316

* gh-16312:
  Use HTTPS for external links from XML files where possible

Closes gh-16312

See gh-16312

* gh-16311:
  Polish "Use HTTPS for external links from XML files where possible"
  Use HTTPS for external links from XML files where possible

See gh-16311

See gh-16311

* gh-16283:
  Use HTTPS to link to Apache License

Closes gh-16283

See gh-16283

* gh-16244:
  Polish "Update build and setup configuration to use HTTPS"
  Update build and setup configuration to use HTTPS

Closes gh-16244

See gh-16244

See gh-16244

* gh-16243:
  Polish "Update build and setup configuration to use HTTPS"
  Update build and setup configuration to use HTTPS

Closes gh-16243

See gh-16243

See gh-16243

Closes gh-9385

Closes gh-9280

* pr/9429:
  Upgrade to Spring AMQP 1.6.10

Closes gh-9429

Closes gh-9424

Different versions of Docker produce different responses when building
and tagging an image. On CI, a response with a stream like
"Successfully built 185991ffe24a" followed by a response with a
stream like "Successfully tagged spring-boot-it/centos:6.9-a23bced6"
is received. By default, for the building of an image to be considered
successful, the Docker Java client requires the stream for the last
response item to contain "Successfully built". This means that, on the
CI server, it incorrectly believes that the building of the tagged
image has failed.

This commit uses a custom BuildImageResultCallback that doesn't
require the last response to be the one that has a stream containing
"Successfully built". Instead, it looks back through the error-free
responses (newest to oldest) looking for one with a stream containing
"Successfully built".

CentOS 5 was declared EOL in March 2017 and yum on longer works
out of the box. 6.9 is the latest release of CentOS 6. Tests for
CentOS 7 have not been added as it uses systemd rather than SysVinit.

Closes gh-9395

Closes gh-9073

Calling launch of PropertiesLauncherTests sets the thread context
class loader to an instance of LaunchedURLClassLoader. To avoid this
class loader being used beyond the scope of the test and launcher
that created it, this commit updates PropertiesLauncherTests to
capture the TCCL before each test and restore it after each test.

Closes gh-9378