This commit extends the forceSsl support to redirect any HTML content
to https. Practically speaking, this allows to redirect all browsers to
https when they land on the main page using https. Serving traffic via
http is still allowed as preventing this would break a lot of
existing clients.
To allow to easily run the app locally, forceSsl is false and must be
enabled for any production environment.
Closes gh-473
This commit moves the generation of bundles for snippet and stubs to the
`docs` profile. This allows to successfully build the project when tests
are skipped, as long as the `docs` profile is not active.
Closes gh-665
Note that the custom `CommandLineContentNegotiationStrategy` has been
adapted to the changes in the `ContentNegotiationStrategy` contract done
in https://jira.spring.io/browse/SPR-16624.
Closes gh-648
This commit reverts to `@RequestMapping` as certain endpoints are
invoked with `GET` or `POST`.
This is a temporary measure as we need to figure out and properly
document allowed methods for all endpoints
Closes gh-615
This commit upgrades to Spring Boot 2.0.0.
Please note that this commit does not change metrics names to use new
features of Micrometer yet (see gh-526)
Closes gh-611
This commits upgrade to Kotlin 1.2.20 and uses the new stdlib artifact
names. As a result, 2.0 milestones prior to Spring Boot 2.0.0.RC1 are
no longer supported.
Closes gh-576
This commit replaces Google Analytics with Tag Manager in the official
start.spring.io service instance.
The code section has been moved from the end of the body to the end
of the head section.
Closes gh-525
This commit reuses the `RestTemplateBuilder` infrastructure wherever
a `RestTemplate` is required. This allows to customize the rest template
if necessary.
Closes gh-481
This commit derives the package name of the application from the
artifact's `groupId` and `artifactId`. Previously sources were put in a
package that mirrors the groupId value.
This goes against the "unique package per application" policy that we
try to enforce. Even if the package name value can be customized
manually, deriving it automatically from the values provided in those
fields will help structure codebases.
With this change, the package name is derived like this:
* groupId `com.example`, artifactId `bookmarks` -> package
`com.example.bookmarks`
* groupId `com.example`, artifactId `user-management` -> package
`com.example.usermanagement`
This commit fixes the package name generation on the server, but also
in the web interfaces when the user updates the form fields.
Fixes gh-421
Madhura Bhave