diff options
| author | Tristan Van Berkom <tristan.vanberkom@codethink.co.uk> | 2020-04-30 16:21:19 +0900 |
|---|---|---|
| committer | Tristan Van Berkom <tristan.vanberkom@codethink.co.uk> | 2020-05-04 17:55:32 +0900 |
| commit | d1d002dec836579e0f708ad438a8265070963c51 (patch) | |
| tree | 8e29e2b82bb55987c34c9f3c26d4abbb67333c7a /NEWS | |
| parent | e13275bdd92aae182d7e93f5b916c4fc4fd280f8 (diff) | |
| download | buildstream-d1d002dec836579e0f708ad438a8265070963c51.tar.gz | |
plugin.py: Rework how deprecation warnings are configured.
This is mostly a semantic change which defines how deprecation warnings
are suppressed in a more consistent fashion, by declaring such suppressions
in the plugin origin declarations rather than on the generic element/source
configuration overrides section.
Other side effects of this commit are that the warnings have been enhanced
to include the provenance of whence the deprecated plugins have been used in
the project, and that the custom deprecation message is optional and will
appear in the message detail string rather than in the primary warning text,
which now simply indicates that the plugin being used is deprecated.
Documentation and test cases are updated.
This fixes #1291
Diffstat (limited to 'NEWS')
| -rw-r--r-- | NEWS | 8 |
1 files changed, 8 insertions, 0 deletions
@@ -8,6 +8,14 @@ CLI o `bst shell --build` will now automatically fetch missing sources. +Format +------ + + o BREAKING CHANGE: Now deprecation warnings are suppressed using the `allow-deprecated` + configuration with the plugin origins in project.conf, instead of on the + source/element overrides section (See issue #1291) + + ================== buildstream 1.93.3 ================== |