Spring Boot 1.3.0 RC1 Release Notes

Note	Work in progress. Spring Boot 1.3.0.RC1 has not been released yet.

Spring Boot 1.3.0 RC1 Release Notes

For changes in earlier milestones, please refer to:

Upgrading

Property renames

The error.path property has been renamed to server.error.path.

MVC Stacktrace output

Stack trace information is now never included when reporting errors. If you want Spring Boot 1.2 behavior set ` error.include-stacktrace to on-trace-param.

Tomcat session storage

By default tomcat no longer saves session data in /tmp. If you want to use persistent sessions with Tomcat set the server.session.persistent property to true. The server.session.store-dir can be used to save files in a specific location.

Spring HATEOAS

The spring.hateoas.apply-to-primary-object-mapper property has been removed as the Spring HATEOAS auto-configuration has been reworked such that it no longer affects the context’s primary ObjectMapper. It has been replaced with a property named spring.hateoas.use-hal-as-default-json-media-type which controls whether or not the Spring HATEOAS HTTP message converter will handle requests for application/json in addition to requests for application/hal+json.

Maven spring-boot:run resources

The Spring Boot Maven plugin no longer adds src/main/resources directly to the classpath when using spring-boot:run. If you want live, in-place editing we recommend using Devtools. The addResources property can be set in your pom.xml if you want to restore Spring Boot 1.2. behavior.

Upgrading from 1.2.x

See the instructions in the M1 release notes for upgrade from 1.2.x.

New and Noteworthy

X-Forwarded-For header support

X-Forwarded-For header support is now provided for Jetty and Undertow. Tomcat support has also been refreshed so that a single server.proxy-peer-address property can be set to true if X-Forwarded-For headers should be respected. Spring Boot will detect deployments to Cloud Foundry or Heroku and automatically enable support.

Session storage

The location to save persistent session data can now be specified using the server.session.store-dir property. You need to also set server.session.persistent to true.

TraceWebFilter options

The actuator TraceWebFilter (use to trace HTTP request/response details) can now log more information. Use the management.trace.include property to configure the options that you want to include (see the TraceProperties.Include enum).

Logging

The “root cause first” logging change made in M3 has been reverted. Stacktraces now appear in the standard format. You can set logging.exception-conversion-word if you prefer “root cause first”.

Fully Executable Jars

Fully executable JAR support has been refined to allow the INIT INFO section to be customized. See the updated reference documentation for details.

Error handling

The error.include-stacktrace property can now be used to determine when stack trace attributes should be included. Options are never, always or on-trace-param (with never being the default).

Spring CLI

The spring CLI command can now generate executable WAR files. Use $ spring war <filename.war> <script.groovy>.

Miscellaneous

The following miscellaneous updates are also included with Spring Boot 1.3 RC1:

Active profiles are now printed to output log when your application starts.
The spring.main.banner-mode property can be used to switch between CONSOLE, LOG or OFF output.
Remote DevTools can now work behind a proxy server (see the spring.devtools.devtools.proxy.* properties)

TODO

Auto-configuration of WebSocket message converter
Auto-configuration of Jackson’s parameter names module
Spring Security header defaults
Revert stacktrace order
https://github.com/spring-projects/spring-boot/issues/4227#issuecomment-149562276
war command
initOptions on fully exec jars
Maven addResources
Maven activeProfiles
DelegatingFilterProxy
DB2 driver detection
Template warning not exception
Log patterns
error properties now renamed server.error