* zero-restructure:
Package restructure
Further maven module restructure
Polish and fix sonar warnings
Minor pom tweaks
Add structure 101 project
Remove servet/filter class tangle
Restructure autoconfigure project
Remove tangles from core + minor polish
Restructure packages
Minor change to code formatting
Move @AssertMissingBean to tests
Polish Javadoc
Restructure 'bootstrap' to use 'zero'
Source formatting and clean-up
Restructure projects layout
Call repositorySystem.readArtifactDescriptor before resolving
launcher dependencies. This change allows remote snapshot dependencies
that are not in the local repo to be downloaded.
Issue: #52901751
Modify TomcatEmbeddedServletContainerFactory to ensure that the
system ClassLoader is not considered when loading classes.
This is required to fix issues when working with executable JARs
created with the maven plugin.
Add a setup profile allowing the maven plugin to be build alone.
Required to prevent 'unresolveable build extension' errors on a
fresh checkout.
Issue: #52091115
Develop a maven plugin that can be used to package executable jar/war
archives. The plugin is intended to be used as a drop-in replacement
for the standard maven-jar-plugin. To use the plugin declare it with
<extensions>true</extensions> then set the project type to
'executable-jar' or 'executable-war'.
Configuration options for 'executable-war' generation are intentionally
much more limited then the standard maven-war-plugin (for example
overlays are not supported). It is anticipated that builds requiring
complex configuration will continue to use the standard plugin in
combination with a custom assembly.
Issue: #52091115
It appears that some machines break when looking for ConnectionException,
but not SocketException, both of which are IOExceptions. This seems to make
tests pass on more machines without compromising the intentions of the API.
[BS-162]
Numerous changes to the actuator project, including:
- Specific Endpoint interface
- Spring MVC/Enpoint adapter
- Management server context changes
- Consistent auto-configuration class naming
- Auto-configuration ordering
- Javadoc, code formatting and tests
Update OnBeanCondition and OnMissingBeanCondition to work better
with @Configuration classes and to support an optional considerHierarchy
annotation value.
The class value for conditions can now also be inferred when used on
@Bean methods.
Phillip Webb
Dave Syer
Greg Turnquist
Gonçalo Silva and Scott Andrews