| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds the concept of a 'platform', a centralized place in which
environment-specific information will be managed, and provides common
initialization logic for most "standard" apps.
As part of the common initialization, other parts of core have also
been reworked:
- HTTP-related unmarshallers and path matchers have been factored out
from core.json to a new core.rest.directives package (core.json
extends those unmarshallers and matchers for backwards
compatibility)
- CORS handling has also been moved to a dedicated utility trait
- Some custom headers have been moved from raw headers to typed ones
in core.rest.headers
- The concept of a "reporter" has been introduced. A reporter is a
context-aware combination of tracing and logging. It is intended to
issue diagnostic messages that can be traced across service
boundaries.
Closes #192
Closes #195
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will affect development workflow: instead of running `sbt
release` to tag and publish a new version, the release process is now
as follows:
1. Create a git tag on a revision that should be published. The tag
must be in the format `v[0-9].*`
2. Push the tag to GitHub `git push --tags`
3. CI will build that tag and publish the resulting binary to our
artifactory
Since the new sbt settings do not enable advanced or risky language
features globally anymore (such as higher kinds, reflective calls and
implicit conversions), the other changes in this PR either import
language features locally or refactor the code to avoid using them
entirely.
|
