Re: [NOTICE] master now on Java 8

Well, the thing is the XStream docs suggest it is OK with the version we're using, so I believe we need to change some of the marshalling config opts rather than continuing to upgrade. Happy for people to experiment, though... On Fri, 26 May 2017 at 11:52 Geoff Macartney <

Re: [NOTICE] master now on Java 8

Thanks for the reminder Andrew, that is a good point. I wonder if things would work any better with XStream 1.4.10 (the latest)? On Fri, 26 May 2017 at 16:20 Andrew Kennedy < andrew.kenn...@cloudsoftcorp.com> wrote: > I believe that lambdas do not get persisted properly at the moment, which >

Re: [NOTICE] master now on Java 8

I believe that lambdas do not get persisted properly at the moment, which might be worth investigating further. See the BROOKLYN-448 issue for details. - https://issues.apache.org/jira/browse/BROOKLYN-448 Andrew. On Fri, 19 May 2017 at 13:39 Geoff Macartney < geoff.macart...@cloudsoftcorp.com>

[jira] [Commented] (BROOKLYN-477) Add docs for target machine requirements/expectations

[ https://issues.apache.org/jira/browse/BROOKLYN-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026376#comment-16026376 ] ASF GitHub Bot commented on BROOKLYN-477: - Github user aledsage commented on a diff in the pull

[jira] [Commented] (BROOKLYN-477) Add docs for target machine requirements/expectations

[ https://issues.apache.org/jira/browse/BROOKLYN-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026377#comment-16026377 ] ASF GitHub Bot commented on BROOKLYN-477: - Github user aledsage commented on a diff in the pull

[GitHub] brooklyn-docs pull request #192: BROOKLYN-477: add “Provisioned Machine Re...

Github user aledsage commented on a diff in the pull request: https://github.com/apache/brooklyn-docs/pull/192#discussion_r118721957 --- Diff: guide/locations/provisioned-machine-requirements.md --- @@ -0,0 +1,161 @@ +--- +title: Provisioned Machine Requirements

[GitHub] brooklyn-server pull request #672: Bundle uninstall and snapshot

Github user geomacy commented on a diff in the pull request: https://github.com/apache/brooklyn-server/pull/672#discussion_r118721807 --- Diff: core/src/main/java/org/apache/brooklyn/core/mgmt/ha/OsgiArchiveInstaller.java --- @@ -0,0 +1,429 @@ +/* + * Licensed to the

[GitHub] brooklyn-server issue #672: Bundle uninstall and snapshot

Github user geomacy commented on the issue: https://github.com/apache/brooklyn-server/pull/672 Test files attached (both cause the problem described above. [test672a.zip](https://github.com/apache/brooklyn-server/files/1032231/test672a.zip)

[GitHub] brooklyn-server issue #672: Bundle uninstall and snapshot

Github user geomacy commented on the issue: https://github.com/apache/brooklyn-server/pull/672 I have **finally** got round to doing a test on this, sorry to have taken so long. I will attach a couple of zip files here for test purposes, each being a separate -SNAPSHOT

Build failed in Jenkins: brooklyn-server-master #602

See Changes: [aled.sage] BROOKLYN-499: avoid log.warn “no-arg constructor accessible” -- [...truncated 3.79 MB...] [INFO] Finished adding exclusions from SCM ignore

[jira] [Resolved] (BROOKLYN-505) Amazon provisioning fails with "Illegal key size"

[ https://issues.apache.org/jira/browse/BROOKLYN-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aled Sage resolved BROOKLYN-505. Resolution: Fixed Fix Version/s: 0.12.0 Fix is just in docs; no code changes were

[jira] [Commented] (BROOKLYN-505) Amazon provisioning fails with "Illegal key size"

[ https://issues.apache.org/jira/browse/BROOKLYN-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026359#comment-16026359 ] Aled Sage commented on BROOKLYN-505: Thanks [~svet]. We could also add this to the troubleshooting

[jira] [Resolved] (BROOKLYN-499) Warning on rebind - UpdatingNotUpFromServiceProcessIsRunning is protected

[ https://issues.apache.org/jira/browse/BROOKLYN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aled Sage resolved BROOKLYN-499. Resolution: Fixed Fix Version/s: 0.12.0 > Warning on rebind -

[GitHub] brooklyn-server pull request #702: BROOKLYN-499: avoid log.warn “no-arg co...

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

[jira] [Commented] (BROOKLYN-499) Warning on rebind - UpdatingNotUpFromServiceProcessIsRunning is protected

[ https://issues.apache.org/jira/browse/BROOKLYN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026351#comment-16026351 ] ASF GitHub Bot commented on BROOKLYN-499: - Github user asfgit closed the pull request at:

[GitHub] brooklyn-server pull request #704: Adds WindowsYamlTest (unit test)

GitHub user aledsage opened a pull request: https://github.com/apache/brooklyn-server/pull/704 Adds WindowsYamlTest (unit test) Note the `AbstractWindowsYamlTest` is a straightforward move of code from `WindowsYamlLiveTest`. You can merge this pull request into a Git repository by

[GitHub] brooklyn-server issue #703: BROOKLYN-490: propagate failure in LoopOverGroup...

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

[jira] [Commented] (BROOKLYN-490) Failure of LoopOverGroupMembersTestCase doesn't propagate.

[ https://issues.apache.org/jira/browse/BROOKLYN-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026105#comment-16026105 ] ASF GitHub Bot commented on BROOKLYN-490: - Github user neykov commented on the issue:

[jira] [Commented] (BROOKLYN-508) Persistence to aws-ec2:eu-west-1 fails in jclouds, looking up "requested location us-standard"

[ https://issues.apache.org/jira/browse/BROOKLYN-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026099#comment-16026099 ] Aled Sage commented on BROOKLYN-508: The reason that jclouds tries to get the URL for "requested

[jira] [Commented] (BROOKLYN-503) Shell.env should work with SaltEntity

[ https://issues.apache.org/jira/browse/BROOKLYN-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026085#comment-16026085 ] Aled Sage commented on BROOKLYN-503: Thanks for reporting this - agreed the salt entity should

[jira] [Resolved] (BROOKLYN-490) Failure of LoopOverGroupMembersTestCase doesn't propagate.

[ https://issues.apache.org/jira/browse/BROOKLYN-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aled Sage resolved BROOKLYN-490. Resolution: Fixed Fix Version/s: 0.12.0 > Failure of LoopOverGroupMembersTestCase doesn't

[jira] [Commented] (BROOKLYN-490) Failure of LoopOverGroupMembersTestCase doesn't propagate.

[ https://issues.apache.org/jira/browse/BROOKLYN-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025950#comment-16025950 ] ASF GitHub Bot commented on BROOKLYN-490: - Github user asfgit closed the pull request at:

[GitHub] brooklyn-server pull request #703: BROOKLYN-490: propagate failure in LoopOv...

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

[GitHub] brooklyn-server issue #693: jclouds TemplateOptions type coercions

Github user neykov commented on the issue: https://github.com/apache/brooklyn-server/pull/693 The exception ^ was due to me not specifying all of the fields in `windowsConfiguration`, leaving out one of the `boolean` arguments. --- If your project is set up for it, you can reply to