GitHub user aledsage opened a pull request:

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

    Pr173/yaml config tests

    Part of #173 - please review + merge here, to decrease the size of PR #173 !
    
    Builds on #174 (the config rename is required), so please review + merge 
that first.
    
    This just tests the existing functionality. Note there are a couple of 
disabled tests, which demonstrate existing limitations.

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

    $ git pull https://github.com/aledsage/brooklyn-server 
pr173/yaml-config-tests

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

    https://github.com/apache/brooklyn-server/pull/175.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 #175
    
----
commit fcfcacfe91c41462b7f97a75721669acf596732e
Author: Aled Sage <[email protected]>
Date:   2016-05-26T09:39:52Z

    Rename TestEntity confMapThing.obj to confMapObjThing
    
    The previous name caused problems because there is also a 
    “confMapThing” of type MapConfigKey. That has special behaviour,
    where it looks up any config with that prefix - so it picked up
    any config defined against confMapThing.obj as well.

commit 7e66c2099519d59336ff7ae014a892b37e369cc2
Author: Aled Sage <[email protected]>
Date:   2016-06-01T16:57:50Z

    Disable EntityConfigTest.testGetConfigNonBlocking

commit c04658760bb8ce21a4d2be1d0d3cd374503c880b
Author: Aled Sage <[email protected]>
Date:   2016-05-26T09:40:37Z

    AbstractYamlTest.setUp/tearDown throws Exception

commit 73e4469f7865b2986f64b09c77815f200c4acb53
Author: Aled Sage <[email protected]>
Date:   2016-05-26T10:01:30Z

    Add YAML config tests

----


---
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.
---

Reply via email to