This is an automated email from the ASF dual-hosted git repository. duncangrant pushed a commit to branch ruby-3 in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
commit 15afba3a4f3976df9aff583861f1677bd1c4e7b2 Merge: 7d808f6 892400e Author: Alex Heneveld <[email protected]> AuthorDate: Tue Sep 4 14:31:08 2018 +0100 Merge commit '892400e4' into release-5.0-reverted-222 LICENSE | 8 +++++++- guide/misc/release-notes.md | 25 +++++++++++++++++++++++++ 2 files changed, 32 insertions(+), 1 deletion(-) diff --cc guide/misc/release-notes.md index 970b86f,afa6355..4b3e546 --- a/guide/misc/release-notes.md +++ b/guide/misc/release-notes.md @@@ -17,8 -16,32 +17,33 @@@ to Brooklyn's commercial users for fund ### Backwards Compatibility -Changes since {{ book.brooklyn_version_stable }}: +Changes since 0.12.0: + 1. BOM files that do not declare a version now give the version of the bundle to their entities, + rather than the default `0.0.0-SNAPSHOT` version. + When loading types, the version can now be specified as any Brooklyn-valid version string + equivalent to the OSGi version (e.g. `1-SNAPSHOT` or `1.0.0.SNAPSHOT`). + + 1. Some catalog methods may return the same type multiple times, if contained in multiple bundles. + Previously only one of the bundle's definition of the type was returned. + Except for anonymous bundles it is no longer allowed to have give items with the same name and version. + (This is required to prevent Brooklyn from getting in to a state where it cannot rebind.) + + 1. Value resolution is now supported for config default values. Previously these would be coerced but + not resolved beyond that -- i.e. TaskFactory values would not have tasks evaluated, and Map and + Collection values would not be deeply resolved with their internals coerced or evaluated. + This makes the semantics of default values consistent with explicit config values. + + 1. Deep config resolution of nested items has changed to be consistent with when deep config applies. + Deep config applies to maps and collections, but previously any Iterable contained therein + would have a recursive deep config evaluation. Now this is limited to nested Collection types + (Lists, Sets, etc) and Maps; nested Iterable instances that are not also Collections are + no longer traversed and resolved recursively. This makes their nested resolution consistent + with when such instances are non-nested config value, as deep resolution was not applied there. + This mainly affects PortRange, where previously if set directly on a config key it would return + the PortRange value but if accessed in a map such as `shell.env` any non-default value would + be expanded as a list `[1, 2]` (but default values would not be expanded, as per previous point, + but now they are). -For changes in prior versions, please refer to the release notes for those versions by selecting the one you are interested in on the left menu. +For changes in prior versions, please refer to the release notes for +[0.12.0]({{ site.path.v }}/0.12.0/misc/release-notes.html).
