GitHub-Spring/spring-boot - spring-boot - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Phillip Webb	fd5c43cdc9	Separate endpoint concerns Update endpoint code to provide cleaner separation of concerns. Specifically, the top level endpoint package is no longer aware of the fact that JMX and HTTP are ultimately used to expose endpoints. Caching concerns have also been abstracted behind a general purpose `OperationMethodInvokerAdvisor` interface. Configuration properties have been refined to further enforce separation. The `management.endpoint.<name>` prefix provides configuration for a single endpoint (including enable and cache time-to-live). These properties are now technology agnostic (they don't include `web` or `jmx` sub properties). The `management.endpoints.<technology>` prefix provide exposure specific configuration. For example, `management.endpoints.web.path-mapping` allow endpoint URLs to be changed. Endpoint enabled/disabled logic has been simplified so that endpoints can't be disabled per exposure technology. Instead a filter based approach is used to allow refinement of what endpoints are exposed over a given technology. Fixes gh-10176	8 years ago
Johnny Lim	bd0dcfb172	Utilize StandardCharsets Closes gh-10972	8 years ago
Phillip Webb	c55b5d7111	Polish	8 years ago
Andy Wilkinson	6f55b57855	Make discovery of additional config metdata more robust with Gradle Previously, the configuration metadata annotation processor relied upon an additional metadata file have been copied to an output location. When building with Gradle, it's the processResources task that performs this copy and there is no guarantee that it will have run before the compileJava task unless an explicit dependency betwee the two tasks has been configured. If a project is built using Gradle's parallel build support, the likelihood of this required ordering not occurring increases. This commit updates the configuration metadata annotation processor to consider a new annotation processor option when looking for the additional config metadata file. The Gradle plugin has been updated to provide this option as a compiler argument. The option is only provided when the annotation processor is found on the compilation classpath to avoid a warning from javac's annotation processing about the use of an option that is not supported by any of the available annotation processors. Closes gh-9755	8 years ago
Stephane Nicoll	56afc25304	Allow to customize the path of a web endpoint This commit introduces a endpoints.<id>.web.path generic property that allows to customize the path of an endpoint. By default the path is the same as the id of the endpoint. Such customization does not apply for the CloudFoundry specific endpoints. Closes gh-10181	8 years ago
Andy Wilkinson	2b426c30a6	Polish “Remove explicit type arguments” Closes gh-10494	8 years ago
Johnny Lim	6168fae720	Remove explicit type arguments See gh-10494	8 years ago
Johnny Lim	5aa32b3d0f	Polish Closes gh-10636	8 years ago
Phillip Webb	748e0779b6	Update copyright year for changed files	8 years ago
Phillip Webb	0ba4830b4f	Relocate projects to spring-boot-project Move projects to better reflect the way that Spring Boot is released. The following projects are under `spring-boot-project`: - `spring-boot` - `spring-boot-autoconfigure` - `spring-boot-tools` - `spring-boot-starters` - `spring-boot-actuator` - `spring-boot-actuator-autoconfigure` - `spring-boot-test` - `spring-boot-test-autoconfigure` - `spring-boot-devtools` - `spring-boot-cli` - `spring-boot-docs` See gh-9316	8 years ago

... 4 5 6 7 8