Build failed in Jenkins: brooklyn-master-build #1161

See -- [...truncated 3.31 MB...] 2017-07-20 07:59:17,653 WARN Task Task[sensor ti6bvkxco9:service.notUp.indicators]@xfop2DfY is being finalized before completion 2017-07-20 07:59:

[GitHub] brooklyn-server pull request #769: Fix feature install bundle version issue

GitHub user grkvlt opened a pull request: https://github.com/apache/brooklyn-server/pull/769 Fix feature install bundle version issue Fixes issue with installing bundles, causing the following error: ``` karaf@brooklyn()> feature:install -r jclouds-api-route53 Error execu

[GitHub] brooklyn-server issue #769: Fix feature install bundle version issue

Github user neykov commented on the issue: https://github.com/apache/brooklyn-server/pull/769 LGTM --- 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 th

[GitHub] brooklyn-server pull request #770: Add null checks to Azure default network

GitHub user Graeme-Miller opened a pull request: https://github.com/apache/brooklyn-server/pull/770 Add null checks to Azure default network You can merge this pull request into a Git repository by running: $ git pull https://github.com/Graeme-Miller/brooklyn-server fix_npe_a

[GitHub] brooklyn-server issue #769: Fix feature install bundle version issue

Github user neykov commented on the issue: https://github.com/apache/brooklyn-server/pull/769 Tests pass, merging. --- 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 wis

[GitHub] brooklyn-server pull request #769: Fix feature install bundle version issue

Github user asfgit closed the pull request at: https://github.com/apache/brooklyn-server/pull/769 --- 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 featur

[GitHub] brooklyn-server issue #770: Add null checks to Azure default network

Github user neykov commented on the issue: https://github.com/apache/brooklyn-server/pull/770 Tests are passing. Merging. --- 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

[GitHub] brooklyn-server pull request #770: Add null checks to Azure default network

Github user asfgit closed the pull request at: https://github.com/apache/brooklyn-server/pull/770 --- 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 featur

[GitHub] brooklyn-server pull request #771: [WIP] Updates karaf to 4.1.1

GitHub user m4rkmckenna opened a pull request: https://github.com/apache/brooklyn-server/pull/771 [WIP] Updates karaf to 4.1.1 * Jetty update to 9.3.14.v20161028 You can merge this pull request into a Git repository by running: $ git pull https://github.com/m4rkmckenna/brooklyn

[GitHub] brooklyn-server issue #771: [WIP] Updates karaf to 4.1.1

Github user neykov commented on the issue: https://github.com/apache/brooklyn-server/pull/771 :+1: glad to see so few changes needed. --- 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 feat

[GitHub] brooklyn-dist pull request #101: [WIP] Update logging config for log4j2 due ...

GitHub user m4rkmckenna opened a pull request: https://github.com/apache/brooklyn-dist/pull/101 [WIP] Update logging config for log4j2 due to karaf update (see https://github.com/apache/brooklyn-server/pull/771) You can merge this pull request into a Git repository by running:

[GitHub] brooklyn-server issue #771: [WIP] Updates karaf to 4.1.1

Github user m4rkmckenna commented on the issue: https://github.com/apache/brooklyn-server/pull/771 @neykov Biggest change is the logging which im working through in https://github.com/apache/brooklyn-dist/issues/101 --- If your project is set up for it, you can reply to this email an

[GitHub] brooklyn-dist issue #101: [WIP] Update logging config for log4j2 due to kara...

Github user neykov commented on the issue: https://github.com/apache/brooklyn-dist/pull/101 If we are changing logging providers, perhaps it's the right time to look at using logback, as was the initial plan? Any preferences here for log4j2 vs logback? --- If your project is set

[GitHub] brooklyn-dist issue #101: [WIP] Update logging config for log4j2 due to kara...

Github user m4rkmckenna commented on the issue: https://github.com/apache/brooklyn-dist/pull/101 I have a preference for log4j2 as I know it better and I have a plan to use the JSON Layout for something Do you think logback is better? --- If your project is set up for it, yo

[GitHub] brooklyn-dist issue #101: [WIP] Update logging config for log4j2 due to kara...

Github user tbouron commented on the issue: https://github.com/apache/brooklyn-dist/pull/101 +1 on log4j2, but it's personal preference --- 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 fe