Closed
Description
- Update
pom.xml
- Use new version (also update the comments)
- Read the change logs
- Spring Boot
- https://spring.io/blog/2015/12/18/spring-boot-1-3-1-and-1-2-8-available-now
- https://spring.io/blog/2016/01/22/spring-boot-1-3-2-released
- https://spring.io/blog/2016/02/26/spring-boot-1-3-3-and-1-4-0-m1-available-now
- https://spring.io/blog/2016/05/06/spring-boot-1-3-4-released
- https://spring.io/blog/2016/05/10/spring-boot-1-3-5-released
spring
(4.2.3.RELEASE -> 4.2.6.RELEASE)spring-security
(4.0.3 -> 4.0.4)liquibase
(3.4.1 -> 3.4.2)jetty
(9.2.11.v20150529 -> 9.2.16.v20160414 because ofjava.lang.UnsupportedOperationException: Use setIncludedMimeTypes or setExcludedMimeTypes instead
)
- Spring Boot
- Migrate
- Compare dependencies
- Try to use
server.server-header
(Spring Boot GH 4461) - Try
server.server-name
property (Spring Boot GH 4504) - Configure dispatcher types (Spring Boot GH 4505)
- Remove
install: true
workaround (Spring Boot GH 4922) (resolution: I don't see the benefits) - Try to use
AuthenticationAuditListener
(resolution: need more investigation and depends on Activate and integrate spring-boot-actuator #86, so we'll back to it later) - Check
*.conf
file permissions on server (Spring Boot GH 4935) (resolution: so hard permissions (0400
) on config file will make our auto-releases harder and I don't see any problem that someone could read the options of JVM)