- 01 Sep, 2016 2 commits
-
-
Phillip Webb authored
-
Stephane Nicoll authored
Closes gh-6780
-
- 31 Aug, 2016 23 commits
-
-
Andy Wilkinson authored
Closes gh-6668
-
Andy Wilkinson authored
Closes gh-6798
-
Andy Wilkinson authored
Closes gh-1309
-
Andy Wilkinson authored
Closes gh-3592
-
Andy Wilkinson authored
* gh-6399: Polish "Provide dependency management for Querydsl" Provide dependency management for Querydsl
-
Andy Wilkinson authored
Closes gh-6399
-
Eddú Meléndez authored
Closes gh-6777 See gh-6399
-
Andy Wilkinson authored
Closes gh-6765
-
Andy Wilkinson authored
Fix mistake introduced during forward merge
-
Andy Wilkinson authored
-
Andy Wilkinson authored
* gh-6759: Polish “Avoid null handler package in JarFile protocol handler registration” Avoid null handler package in JarFile protocol handler registration
-
Andy Wilkinson authored
See gh-6759
-
Phillip Webb authored
Rework commit 4a69755b to remove the need for the ApplicationInfo class. The updated code now uses the auto-configuration class to compute a default persistence unit root location Closes gh-6635
-
hengyunabc authored
Closes gh-6759
-
Andy Wilkinson authored
-
Andy Wilkinson authored
Closes gh-6762
-
Andy Wilkinson authored
Previously, the HAL browser endpoint did not consider the dispatcher servlet’s path (server.servlet-path) when redirecting to browser.html or when updating the API entry point in the served HTML. This commit moves to using ServletUriComponentsBuilder to build the URI for the redirect and the path for the entry point. In the interests of simplicity the logic that sometimes redirected and sometimes forwarded the request has been changed so that it will always perform a redirect. Closes gh-6586
-
Stephane Nicoll authored
This commit improves the run goal to automatically fork the process when devtools is present and log a warning when fork has been disabled via configuration since devtools will not work on a non-forked process. We don't want devtools to kick in for integration tests so the logic has been placed in `RunMojo` requiring a couple of protected methods to override. Closes gh-5137
-
Stephane Nicoll authored
-
Stephane Nicoll authored
Closes gh-6778
-
Stephane Nicoll authored
Closes gh-6770
-
Stephane Nicoll authored
See gh-6792
-
Stephane Nicoll authored
Closes gh-6788
-
- 29 Aug, 2016 4 commits
-
-
Phillip Webb authored
Update @MockBean and @SpyBean to support field generics. Prior to this commit the following fields would fail with a "Duplicate mock definition" exception: @MockBean private IdentityProvider<PasswordIdentity> passwordIdentityProvider; @MockBean private IdentityProvider<Oauth2Identity> oauth2IdentityProvider; Fixes gh-6602
-
Phillip Webb authored
-
Phillip Webb authored
-
Phillip Webb authored
-
- 28 Aug, 2016 1 commit
-
-
Stephane Nicoll authored
-
- 27 Aug, 2016 2 commits
-
-
Stephane Nicoll authored
-
Stephane Nicoll authored
So far, one has to set the "fork" value to both the start and stop goals. Since they have the same name, sharing them in a global configuration element does the trick. However, the plugin also supports auto-detection of the fork value according to other parameters: typically if an agent or jvm arguments are set, forking will be automatically enabled. This is a problem since the stop goal is not aware of that. This commit transmits the value in a property attached to the `MavenProject`. That way, the stop goal can retrieve that value and apply the same defaults. This has the side effect that specifying the fork value isn't necessary anymore. Closes gh-6747
-
- 26 Aug, 2016 8 commits
-
-
Andy Wilkinson authored
Closes gh-6764
-
Andy Wilkinson authored
-
Andy Wilkinson authored
Closes gh-6559
-
Andy Wilkinson authored
-
Andy Wilkinson authored
Previously, BeanTypeRegistry did not correctly determine the type that would be created by a factory bean if that factory bean was returned from a bean method with arguments on a configuration class found via component scanning. The key difference is that bean definitions for bean methods on configuration classes found via component scanning use ASM-based metadata rather than reflection-based metadata. The ASM-based method data does not provide direct access to the Method that will create the bean. In this case, BeanTypeRegistry was falling back to looking for a method with the matching name and no arguments. Therefore, if the bean method had any arguments it would fail to find the method and would, therefore, be unable to determine the type of bean produced by the factory bean. This commit updates BeanTypeRegistry to use logic that is very similar to Spring Framework's ConstructorResolver's resolveFactoryMethodIfPossible method to locate the method that will produce the factory bean. It looks for a single method with the required name with any number of arguments. If it finds multiple methods with the required name and different arguments it returns null, just as ConstructorResolver does. Closes gh-6755
-
Stephane Nicoll authored
* pr/6746: Polish contribution Detect Neo4j bolt driver
-
Stephane Nicoll authored
Closes gh-6746
-
Caleb Cushing authored
Closes gh-6690
-