brooklyn-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [1/2] brooklyn-docs git commit: release notes updated with recent code changes
Date Tue, 14 Nov 2017 08:54:40 GMT
Repository: brooklyn-docs
Updated Branches:
  refs/heads/master 40c59c6c1 -> 23b26ca65

release notes updated with recent code changes


Branch: refs/heads/master
Commit: f97f34dfbc53f55a75304a425bcc467fd4229f02
Parents: ba27cf1
Author: Alex Heneveld <>
Authored: Thu Nov 2 10:22:36 2017 +0000
Committer: Alex Heneveld <>
Committed: Thu Nov 2 11:04:50 2017 +0000

 guide/misc/ | 25 +++++++++++++++++++++++++
 package-lock.json           |  2 +-
 2 files changed, 26 insertions(+), 1 deletion(-)
diff --git a/guide/misc/ b/guide/misc/
index 7dd5009..afa6355 100644
--- a/guide/misc/
+++ b/guide/misc/
@@ -18,5 +18,30 @@ to Brooklyn's commercial users for funding much of this development.
 Changes since {{ book.brooklyn_version_stable }}:
+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
+   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
+   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
+   (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
+   This mainly affects PortRange, where previously if set directly on a config key it would
+   the PortRange value but if accessed in a map such as `shell.env` any non-default value
+   be expanded as a list `[1, 2]` (but default values would not be expanded, as per previous
+   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.
diff --git a/package-lock.json b/package-lock.json
index c6663e0..7823ee4 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,6 +1,6 @@
   "name": "brooklyn-docs",
-  "version": "0.13.0",
+  "version": "1.0.0",
   "lockfileVersion": 1,
   "requires": true,
   "dependencies": {

View raw message