[GitHub] brooklyn-server pull request #424: BROOKLYN-383: fix json serialisation of t...

2016-11-16 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/brooklyn-server/pull/424


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] brooklyn-server pull request #424: BROOKLYN-383: fix json serialisation of t...

2016-11-10 Thread aledsage
GitHub user aledsage opened a pull request:

https://github.com/apache/brooklyn-server/pull/424

BROOKLYN-383: fix json serialisation of tasks

* Also do the same for policies, enrichers and feeds.
* Adds AbstractEntityAdjunct.getEntity() to make that easier.
* Adds TestEntity.sleepEffector

And tests xml persistence of a task, while I'm at it.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/aledsage/brooklyn-server BROOKLYN-383

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/brooklyn-server/pull/424.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #424


commit d3720c9a6038f3bcd9addeb6404df32667cfb44d
Author: Aled Sage 
Date:   2016-11-10T13:18:43Z

BROOKLYN-383: fix json serialisation of tasks

* Also do the same for policies, enrichers and feeds.
* Adds AbstractEntityAdjunct.getEntity() to make that easier.
* Adds TestEntity.sleepEffector

commit 7d0bb562cd5332a7cf0bac8c0f00fbe728d1861a
Author: Aled Sage 
Date:   2016-11-10T13:19:16Z

Test XML persistence of task




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---