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

See -- [...truncated 3.17 MB...] 2017-06-24 01:00:31,231 WARN Task Task[sensor yv03s0d6u1:]@w619At9c is being finalized before completion 2017-06-24 01:00:31,231 WARN Task Task[se

[GitHub] brooklyn-docs pull request #144: Configuring logging from karaf distribution...

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

[GitHub] brooklyn-docs issue #201: Update location structure

Github user bostko commented on the issue: https://github.com/apache/brooklyn-docs/pull/201 Looks good. --- 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

[GitHub] brooklyn-docs pull request #201: Update location structure

GitHub user drigodwin opened a pull request: https://github.com/apache/brooklyn-docs/pull/201 Update location structure Updates the structure from #119. You can merge this pull request into a Git repository by running: $ git pull https://github.com/drigodwin/brooklyn-docs upda

Build failed in Jenkins: brooklyn-client-master #57

See Changes: [thomas.bouron] Allow catalog item (YAML or bundle) to be force-updated via query string -- [...truncated 7.63 KB...] [INFO] Exclude: **/*_rsa.pub [INFO]

[GitHub] brooklyn-client pull request #55: Allow catalog item to be force-updated via...

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

[GitHub] brooklyn-client issue #55: Allow catalog item to be force-updated via query ...

Github user m4rkmckenna commented on the issue: https://github.com/apache/brooklyn-client/pull/55 Tested locally merging now --- 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 enabl

[GitHub] brooklyn-server pull request #744: Allow catalog item to be force-updated vi...

Github user asfgit closed the pull request at: https://github.com/apache/brooklyn-server/pull/744 --- 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-docs issue #144: Configuring logging from karaf distribution of Apa...

Github user bostko commented on the issue: https://github.com/apache/brooklyn-docs/pull/144 @tbouron I included @geomacy note. --- 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 ena

[GitHub] brooklyn-docs pull request #183: [For Review] Details on configuring logging...

Github user bostko closed the pull request at: https://github.com/apache/brooklyn-docs/pull/183 --- 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

[GitHub] brooklyn-docs issue #183: [For Review] Details on configuring logging for OS...

Github user bostko commented on the issue: https://github.com/apache/brooklyn-docs/pull/183 Squash changes into https://github.com/apache/brooklyn-docs/pull/144 --- 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 proj

[GitHub] brooklyn-docs pull request #119: Opening ports for Security Group based loca...

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

[GitHub] brooklyn-server pull request #744: Allow catalog item to be force-updated vi...

Github user tbouron commented on a diff in the pull request: https://github.com/apache/brooklyn-server/pull/744#discussion_r123742309 --- Diff: rest/rest-api/src/main/java/org/apache/brooklyn/rest/api/CatalogApi.java --- @@ -67,7 +67,7 @@ @ApiResponse(code = 400, m

[GitHub] brooklyn-server pull request #744: Allow catalog item to be force-updated vi...

Github user m4rkmckenna commented on a diff in the pull request: https://github.com/apache/brooklyn-server/pull/744#discussion_r123740886 --- Diff: rest/rest-api/src/main/java/org/apache/brooklyn/rest/api/CatalogApi.java --- @@ -67,7 +67,7 @@ @ApiResponse(code = 40

[GitHub] brooklyn-docs issue #198: [WIP] Versioning

Github user ahgittin commented on the issue: https://github.com/apache/brooklyn-docs/pull/198 Thanks @drigodwin, all addressed. Should not be merged until after https://github.com/apache/brooklyn-server/pull/743 . Also added explanation about the `0` minor/patch versions as p

[GitHub] brooklyn-server issue #363: YOML = YAML object mapping language [BIG!]

Github user ahgittin commented on the issue: https://github.com/apache/brooklyn-server/pull/363 Any update @aledsage ? Was it was reviewed the second week of May as planned and there were no comments? ;) I'd like to use this for the `catalog.bom` syntax. Instead I'm having

[GitHub] brooklyn-server issue #742: DefaultAzureArmNetworkCreator improvements

Github user aledsage commented on the issue: https://github.com/apache/brooklyn-server/pull/742 Merged. @neykov (cc @Graeme-Miller) thanks for pointer to your comments in (the already merged) #739. We should address those separately, in a new PR. --- If your project is set u

[GitHub] brooklyn-server pull request #742: DefaultAzureArmNetworkCreator improvement...

Github user asfgit closed the pull request at: https://github.com/apache/brooklyn-server/pull/742 --- 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-client pull request #55: Allow catalog item to be force-updated via...

GitHub user tbouron opened a pull request: https://github.com/apache/brooklyn-client/pull/55 Allow catalog item to be force-updated via query string flag on the REST API This is required by https://github.com/apache/brooklyn-server/pull/744 You can merge this pull request into a Git

[GitHub] brooklyn-server pull request #744: Allow catalog item to be force-updated vi...

GitHub user tbouron opened a pull request: https://github.com/apache/brooklyn-server/pull/744 Allow catalog item to be force-updated via query string flag on the REST API # Issue When `POST`ing a catalog item (YAML file) with an ID and version to already exist, the REST API

Re: Bundles in Brooklyn

Hi Aled, On 22 June 2017 at 18:51, Aled Sage wrote: > _*Business Case (aka value to end-users)*_ > It would be good to be clearer on the user-value we deliver from this (but > please shout if others think that is already clear enough). > I have a fairly simple use case. At the moment (and I may

Re: Bundles in Brooklyn

Aled- Hi -- inline On 22/06/2017 18:51, Aled Sage wrote: +1 to this approach, but I suspect there's a lot more to discuss/plan. Great list of questions. We don't need these solved now for the immediate proposal but I think we are reaching a consensus even on tricky longer-term issues which

Re: Versions in Brooklyn

Aled- Well spotted. I only realised when implementing that the bi-di didn't quite hold where minor/patch versions were omitted because OSGi infers these as 0 (this seems to be true whether or not there is a qualifier). So 1.0 and 1.0.0 in OSGi are the same. This means we have two options: