The main metadata endpoint is available at the root "/" path, for JSON
compatible media types. This endpoint is often requested by CLI and
IDEs. Initializr is setting HTTP response headers to tell clients to
cache the response body.
With this current situation, several HTTP caching issues can happen.
1. Since many formats are available at the same path, proxies can cache
the response body and redistribute it to many clients, even if they
don't request the same media type. To fix that, we need to add a
`Vary: Accept` response header; with that, proxies will cache responses
but take into account that different Accept request headers might yield
different responses.
2. Browsers have very specific caching implementations, and exposing
that metadata endpoint on "/" and at the same time an HTML page will
create issues related to HTTP caching. Navigation and refreshes might
result with strange problems. To fix that, we need to reinstate the
`/metadata/client` endpoint as a first class citizen (and not just a
redirect). This way, Web UIs can freely use that path to request the
metadata, without risking caching issues.
See gh-914
This commit provides a better test infrastructure when JUnit 5 is
available:
* The default test class uses JUnit Jupiter API
* The vintage engine that the Spring Boot starter provides is excluded
so that only the Junit Jupiter API is available on the classpath
Closes gh-905
In particular, this commit replaces the GradleKts dedicated build system
in favor of a dedicated build system dialect.
Closes gh-851
Co-authored-by: Andy Wilkinson <awilkinson@pivotal.io>
This commit adds support for configuring several tasks at once using
a type. It also migrates the Kotlin support so that, instead of
configuring compileKotlin and compileTestKotlin, it configures all
tasks of type KotlinCompile at once.
See gh-890
This commit extends the build system and platform conditions to allow
for several values to be specified. Those conditions match if any of
the provided value matches.
Closes gh-888
