Really fix it
Remove accidental commit
Favor groovy.jar instead of groovy-all.jar

Update CLI application to use groovy.jar rather than groovy-all.jar.
This prevents classloading issues when a user project @Grabs groovy-ant.
Revert "Re-add Spring-Boot-Commit-Id to MANIFEST.MF of created jars"

This reverts commit 498ca076989742b2d95fa9c3da0950d0f0f3669c.

Removed due to eclipse failures.
Increase whitespace around password logging

Increase the whitespace to make the password easier to find in the log.
Update eclipse formatter XML

Update the eclipse formatter XML to align it with the project specific
settings files. Also corrected the information in CONTRIBUTING.md
Detect Tomcat start failures

Detect if the tomcat container fails to start and propagate an
exception to the caller.
Return early if no plugins should be disabled
Add useful features to CliTester
Add "integration" profile in Maven build

By default it is on, but you can switch it
off (`-P '!integration'`) to ignore integration tests
and get a faster build.

.travis.yml uses this feature so that it doesn't keep
failing on a timeout.
Rename spring-boot-starter-shell-crsh to spring-boot-starter-shell-remote
Remove tomcat dependencies from sample unless needed
Set default log levels same for all systems
Add starter dependency to jdbc for parity
Update main class to reflect use of JarLauncher

b19f6bb238 updated the CLI so that it should be launched using Spring
Boot Loader's JarLauncher, however the spring and spring.bat shell
scripts were not updated so they still launched the CLI by using
SpringCli as the main class. This led to a NoClassDefFoundError
as none of the dependencies in the jar's /lib directory could be
found.

This commit updates the two shells scripts to use JarLauncher as the
main class.
Use legal java.util.logging levels in logging.properties
Jpa auto configuration updates for new Spring Data release

User now gets @EnableSpringDataWebSupport for free in any
autoconfigured JPA webapp.

[Fixes #53028329] [bs-216]
Explicitly add servlet API to actuator sample
Flush output streams in capture

Avoids possible test failures owing to unflushed buffers
Add support for @GrabResolver to AetherGrapeEngine

@GrabResolver can now be used to add a repository to the list that is
used for dependency resolution. Any repository that is added via the
annotation will then be available for the lifetime of the
AetherGrapeEngine instance. In reality, this equates to the lifetime
of the Boot application. This is in keeping with the documented default
behaviour [1]: "By default, the grape subsystem is shared globally, so
added resolvers will become available for any subsequent grab calls".

[1] - http://groovy.codehaus.org/api/groovy/lang/GrabResolver.html

[bs-345]
[60145036]