[GitHub] brooklyn-server issue #873: Upgrade types and bundles as per bundle manifest...

2017-11-07 Thread ahgittin
Github user ahgittin commented on the issue: https://github.com/apache/brooklyn-server/pull/873 Thanks @aledsage @robertgmoss - comments addressed and merged ---

[GitHub] brooklyn-server issue #873: Upgrade types and bundles as per bundle manifest...

2017-11-06 Thread robertgmoss
Github user robertgmoss commented on the issue: https://github.com/apache/brooklyn-server/pull/873 LGTM ---

[GitHub] brooklyn-server issue #873: Upgrade types and bundles as per bundle manifest...

2017-11-03 Thread robertgmoss
Github user robertgmoss commented on the issue: https://github.com/apache/brooklyn-server/pull/873 I have tested rebinding using the [brooklyn-etcd](https://github.com/brooklyncentral/brooklyn-etcd) entity, where the following was added to its `pom.xml`: ```

[GitHub] brooklyn-server issue #873: Upgrade types and bundles as per bundle manifest...

2017-11-02 Thread ahgittin
Github user ahgittin commented on the issue: https://github.com/apache/brooklyn-server/pull/873 Have patched the known gap around entity spec. Those tests now passing. That required a surprising series of tweaks: to how EntitySpec is resolved/persisted, to how default

[GitHub] brooklyn-server issue #873: Upgrade types and bundles as per bundle manifest...

2017-11-01 Thread ahgittin
Github user ahgittin commented on the issue: https://github.com/apache/brooklyn-server/pull/873 retest this please non-det failure: ``` Error Message expected one element but was: <{myKey=myDefault}, {myKey=valIsV1}> Stacktrace