Spring Boot 1.3.0 M2 Release Notes

Spring Boot 1.3.0 M2 Release Notes

• v1.3.0 M1

Upgrading from Spring Boot 1.3.0 M1

Please also see the upgrade instructions in the 1.3.0.M1

Property renames

The following application.properties keys have been renamed to improve consistency: * spring.view. to spring.mvc.view. * spring.pidfile to spring.pid.file * server.session-timeout to server.session.timeout

HTTP response compression

Spring Boot 1.2 supported native response compression for Tomcat users, or compression using Jetty’s GZipFilter for users of Jetty, Tomcat, and Undertow. Motivated by the Jetty team’s deprecation of their gzip filter, Spring Boot 1.3 replaces this with support for native response compression in all three embedded containers. As a result the server.tomcat.compression. and spring.http.gzip. properties are no longer supported. The new server.compression.* properties should be used instead.

Logging

Spring specific configuration

In order to prevent double initialization spring specific log configuration files can now be used. It’s recommended (although not required) that you rename any default log configuration files to use a -spring suffix. For example logback.xml would change to logback-spring.xml.

Initialization failures

In Spring Boot 1.2, if you specified a custom logging configuration file using logging.config and the file did not exist, it would silently fallback to using the default configuration. Spring Boot 1.3 fails due to the missing file. Similarly, if you provided a custom Logback configuration file which was malformed, Spring Boot 1.2 would fall back to its default configuration. Spring Boot 1.3 fails and reports the problems with the configuration to System.err.

Groovy templating

The GroovyTemplateProperties class now extends AbstractTemplateViewResolverProperties and provides additional configuration options. If you currently define a prefix.spring.groovy.template.prefix property to define a custom resource location you should rename it to prefix.spring.groovy.resource-loader-location.

Security for the /health endpoint

Deprecations in Spring Boot 1.3.0 M2

• The protected SpringApplication.afterRefresh method that takes a String[] has been deprecated in favor of a version that takes ApplicationArguments.

New and Noteworthy

TBD

• /logfile actuator endpoint

• SpringVersion class

• ANSI colors in your banner.txt

• PID fail-on-write-error

• Support for jOOQ

• Support for Artemis

• Elasticsearch non local nodes

• Launch script conf file support

• Support for Spring Session

• Driver name support for firebird, DB2 and Teradata

• Extra DB Heath Queries for DB2 and Informix

• useTestClasspath in Maven

• matchers with OutputCapture

• Apache AntLib

• Spring HTTP Resource support

• Logback <springProperty> and <springProfile>

• OutputCapture matchers

• hint meta-data support for properties

• HAL + rest docs

• -default profile

• Flyway and Liquibase actuator endpoints

• server.session config

• ApplicationArguments and ApplicationRunner

JDBC

Spring Boot will now automatically infer the driver class name from the JDBC URL for the following databases:

• DB2

• Firebird

• Teradata

Spring Session

With Spring Session and Spring Data Redis on the classpath, web applications will now be auto-configured to store user sessions in Redis. See the accompanying sample for more information.