Upgrade to Hibernate 5.1, whilst still retaining compatibility with
Hibernate 4.3. This commit introduces the following changes:
* Add SpringPhysicalNamingStrategy to provides lowercase/underscore
table names support. This should be equivalent to the previous
SpringNamingStrategy that was used with Hibernate 4. No
ImplicitNamingStrategy is provided since the Hibernate 5 defaults
appear to be roughly equivalent to the conventions used in Spring
Boot 1.3
spring.jpa.hibernate.naming.
* Migrate `spring.jpa.hibernate.naming-strategy` to
`spring.jpa.hibernate.naming.strategy` and provide additional
properties for physical and implicit.
* Add `spring.jpa.hibernate.use-new-id-generator-mappings` property and
default to `false` when on Hibernate 5 to retain back compatibility.
See gh-2763
Previously, we only had dependency management for
selenium-htmlunit-driver. It depends on three other Selenium modules
for which dependency management was not provided. This means that there
was a risk that a mixture of versions would end up on the classpath.
This commit adds dependency management for the Selenium modules upon
which selenium-htmlunit-driver depends.
Closes gh-5520
While the benign exception that Gemfire outputs is unfortunate, it
isn't sufficient justification for adding dependency management for
Spring Shell.
Closes gh-5444
Previously, JarLauncher considered any entry whose name began with
BOOT-INF/classes/ as being a nested entry. This was incorrect as it
meant that subdirectories of BOOT-INF/classes/ would be added to the
classpath rather than just BOOT-INF/classes/ itself.
This commit updates JarLauncher so that only directory entries with a
name equal to BOOT-INF/classes are used.
Closes gh-5610
Previously, if a JarFile was created from a directory nested inside
another jar file, it would look for the manifest in
pathFromRoot/META-INF/MANIFEST.MF. This is incorrect as, unlike a
JarFile created from a jar file, the archives are one and the same
so the manifests should be too.
This commit updates JarFile so that its aware of how it was created
(direct from a file, from a nested directory, from a nested jar). If
it was created from a file or from a nested jar, it uses its manifest.
If it was created from a nested directory, it uses the manifest of the
root archive.
Closes gh-5609
Previously, `spring.profiles.active` did not trim the individual comma
separate values. As a result, such profile wasn't enabled as expected.
This commit makes sure to trim whitespaces.
Closes gh-5442
* pr/5511:
Polish contribution
Upgrade elasticsearch to 2.2.0
Polish contribution
Deprecate Undertow container's constructors that have a port parameter
Remove unused unsatisfiedDependency.getInjectionPoint() call
Polish contribution
Allow Tomcat's minimum threads to be configured via the environment
Phillip Webb
Mohamed Gazal
Andy Wilkinson
Stephane Nicoll
Eddú Meléndez
John Blum