brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ahgittin <...@git.apache.org>
Subject [GitHub] brooklyn-server pull request #411: Test change to coercion of default config...
Date Mon, 07 Nov 2016 11:29:43 GMT
GitHub user ahgittin opened a pull request:

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

    Test change to coercion of default config values

    Several minor fixes/changes, plus one significant test in https://github.com/apache/brooklyn-server/commit/e9c1f4cbb67d1bd89d1e7d84f8730225047ea337
which highlights a change in behaviour since early Oct
    
    Also see related PR adding this to release notes

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

    $ git pull https://github.com/ahgittin/brooklyn-server default-conversion-notes

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

    https://github.com/apache/brooklyn-server/pull/411.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 #411
    
----
commit dc52db3fc6030dc8e863d6c71794ac7d0bcf732b
Author: Alex Heneveld <alex.heneveld@cloudsoftcorp.com>
Date:   2016-11-07T11:16:56Z

    more conveniences for Strings

commit ef3942166b031b10157bc65708fb533eba4ad60c
Author: Alex Heneveld <alex.heneveld@cloudsoftcorp.com>
Date:   2016-11-07T11:17:15Z

    let yaml tests look in the package where the class is defined
    (so we can group things better than all in the root)

commit e9c1f4cbb67d1bd89d1e7d84f8730225047ea337
Author: Alex Heneveld <alex.heneveld@cloudsoftcorp.com>
Date:   2016-11-07T11:21:41Z

    new test showing changed behaviour of default config value resolution
    
    as included in the release notes

commit c70959099cbd8552dca5b36f573a293a1cd04e1f
Author: Alex Heneveld <alex.heneveld@cloudsoftcorp.com>
Date:   2016-11-07T11:22:14Z

    tidy warnings (deprecation, unused) for camp 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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message