GitHub user aledsage reopened a pull request:
https://github.com/apache/brooklyn-server/pull/59
Test clocker
This has (for testing only) a cut-down version of the Clocker entity and
location structure, and some tests that it works - especially for rebind. The
second commit shows how to fix
https://github.com/brooklyncentral/clocker/issues/237, which motivated doing
this.
(See javadoc in `StubInfrastructure` for a description of the Clocker code
structure that this is testing).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aledsage/brooklyn-server test/clocker
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/59.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 #59
----
commit 292b4cfb8d5b0bbff0f38eba5fc84a1fc9fe4eee
Author: Aled Sage <[email protected]>
Date: 2016-03-11T19:37:13Z
Test the Clocker pattern (of LocationOwner and DynamicLocation)
commit 453183f1d89336ea793aab2edbe05c3b4070104b
Author: Aled Sage <[email protected]>
Date: 2016-03-11T20:50:45Z
Clocker pattern: change how LocationRegistry used
Adds DynamicLocation.register() and .deregister()
commit 9f1a120812895a604f42df29f8e16ec4d4a1ed30
Author: Aled Sage <[email protected]>
Date: 2016-03-17T12:59:24Z
ServerPool: creates/registers single ServerPoolLocation
commit 0b9682b8830df7715bb8b579cfc40a1734f03038
Author: Aled Sage <[email protected]>
Date: 2016-03-18T23:09:04Z
NotUpDiagnostics: donât collect if starting && !up
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
