Spring Boot 1.3.0 M3 Release Notes

Spring Boot 1.3.0 M3 Release Notes

For changes in earlier milestones, please refer to:

• v1.3.0 M1

• v1.3.0 M2

Upgrading from Spring Boot 1.3.0 M2

See instructions in the 1.3.0.M2 release notes for upgrading from 1.3.0 M2

Property renames

The following application.properties keys have been renamed to improve consistency:

• servet.tomcat.accessLogEnabled to server.tomcat.accesslog.enabled

• servet.tomcat.accessLogPattern to server.tomcat.accesslog.pattern

• servet.undertow.accessLogDir to server.undertow.accesslog.dir

• servet.undertow.accessLogEnabled to server.undertow.accesslog.enabled

• servet.undertow.accessLogPattern to server.undertow.accesslog.pattern

Gradle

The Spring Boot Gradle plugin will no longer apply Gradle’s application plugin by default. If you wish to make use of the application plugin you will have to apply it in your build.gradle.

If you do not need the functionality provided by the application plugin, but were using its mainClassName or applicationDefaultJvmArgs properties then you will need to make some minor updates to your build.gradle.

The mainClassName property should now be configured on the springBoot extension, for example:

springBoot {
    mainClassName = 'com.example.YourApplication'
}

applicationDefaultJvmArgs should now be configured in your project’s ext block, for example:

ext {
    applicationDefaultJvmArgs = [ '-Dcom.example.property=true' ]
}

If you were configuring your project’s main class using the main property of the application plugin’s run task, you should move this configuration to the bootRun task instead:

bootRun {
    main = com.example.YourApplication
}

New and Noteworthy

Tip	Check the configuration changelog for a complete overview of the changes in configuration.

Spring Boot CLI

The CLI will now use the repositories configured in Maven’s settings.xml during dependency resolution. For a repository to be used, the profile in which it is declared must be active.

Embedded MongoDB

Auto-configuration for Embedded MongoDB has been added. A dependency on de.flapdoodle.embed:de.flapdoodle.embed.mongo is all that’s necessary to get started. Configuration, such as the version of Mongo to use, can be controlled via application.properties. Please see the documentation for further information.

H2 Web Console

Auto-configuration for H2’s web console has been added. When you are using Spring Boot’s developer tools, adding a dependency on com.h2database:h2 to your web application is all that is necessary to get started. Please see the documentation for further information.

TODO

• Logging

  • logging.pattern.console and logging.pattern.file (#3367)

  • undertow/tomcat access log (#2491)

  • Class packaging information in log (#3398)

  • Logging stack trace order (#3399)

  • Logging jars

  • Log4J2 extras

  • springProfile logback work with a list of name (#3494)

• Unconditional auto-configuration in report (#2209)

• Turn off default health indicator (#2298)

• Exclude auto-config via properties (#2435)

• Auto-configure @EnableConfigurationProperties (#2457)

• Devtools

  • Persistent session across restart (#2490) **

  • Change outside classpath to trigger livereload (#3469)

• Compression (excludeUserAgent #3363)

• Meta-data

  • Meta-data module (#1970)

  • deprecate hint in the meta-data (#3449 and #3543)

  • handle-as new provider (#3457)

  • Better detection of default value

• Messaging

  • Rabbit listener settings (#3475)

  • JMS listener settings (#3519)