A bug in ivy (tickled by maven leaving a pom
but no jar in the local repo) would make the
default Grapes ivy config fail (cannot grab...).
Phil's workaround now has a test case.

Fix the localm2 repository to only consider that a pom exists when
its artifact is contained in the repository.

This prevents a download error that can occur when the local m2
repository contains a POM file but not a JAR.

Issue: #55532358

Issue: #55528242

Change WebMvcAutoConfiguration to use WebMvcConfigurationSupport instead
of HanderAdapter as the @ConditionalOnMissingBean. This allows MVC to
be auto-configured even if you define additional HanderAdapters.

Issue: #55493342

Update HibernateJpaAutoConfiguration to use the ImprovedNamingStrategy
for better table and column names.

Issue: #55261888

Update AutoConfigurationUtils to specifically exclude spring-data-rest
packages from being stored. This prevent missing class errors caused
when Spring Boot attempts to use @ComponentScan packages as the source
for JPA entities and reads annotations that are not on the classpath.

Issue: #55489346

[Fixes #55388726] [bs-292]

The Boot resolver didn't transfer enough of the settings
of the default ChainResolver. Adding a boolean flag was
enough to make the chatter die down for dependencies
that were unneeded.

[Fixes #55358344] [bs-291]

Seems to work. I think the problem was the race conditions
that we hopefully already eliminated. I got an out of memory
error running the samples tests in Eclipse, but then it went
away again (something to look out for).

[Fixes #54925992] [bs-280]

The DispatcherServlet adds a default InternalViewResolver
which was used by some apps, but when the actuator was
available it added an "/error" bean and effectively
switched off the default view resolver. The net fix was
to add an InternalViewResolver at the same time as
adding any other ViewResolvers.

[Fixes #55357516] [bs-290] Actuator UI app cannot serve static index.html

Create a new SpringBootCondition that will log why a condition has
or has not been applied. The removes the need for ConditionLogUtils
and simplifies many of the existing condition implementations.

Issue: #55203236

Update LoggingApplicationContextInitializer to detect the presence of
'--debug' and '--trace' arguments to increase log output.

Using '--debug' will set 'org.springframework.boot' loggers to DEBUG.

Using '--trace' will set 'org.springframework', 'org.apache.tomcat' and
'org.eclipse.jetty' loggers to TRACE.

Issue: #55202588

Change SpringApplicationInitializer interface to include run() args.
Allow initializers to make additional configurations based on the user
supplied arguments.

Issue: #55202588

Rename SpringApplication.defaultCommandLineArgs to defaultArgs for
consistency with the run() method arguments.

Issue: #55202844

Provide a common way to programmatically set log levels regardless of
the underlying log implementation.

Issue: #55202588

* To build site install ruby 1.9.3 and `bundle` in src/main/pages
* Then run src/main/pages/build.sh (from the top level)
* Pages show up in target/pages

Update ConditionalOn annotations :
- Use consistent attribute names for OnClass and OnMissingClass
- Update javadoc
- Rename tests to reflect the annotation rather than the interface

Also add @WebConfiguration as a shortcut for groovy
scripts to get MVC behaviour (without a @Controller)

[#54926366]

# By Chanwit Kaewkasi
* pull23:
  Fix a line ending issue for building on Windows

This reverts commit e8430f61.