Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D4E01200CC5 for ; Tue, 11 Jul 2017 16:24:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D35E616318F; Tue, 11 Jul 2017 14:24:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1F173162FA4 for ; Tue, 11 Jul 2017 16:24:08 +0200 (CEST) Received: (qmail 55525 invoked by uid 500); 11 Jul 2017 14:24:08 -0000 Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@brooklyn.apache.org Delivered-To: mailing list dev@brooklyn.apache.org Received: (qmail 55514 invoked by uid 99); 11 Jul 2017 14:24:08 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jul 2017 14:24:08 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id EFE1BE04AA; Tue, 11 Jul 2017 14:24:07 +0000 (UTC) From: m4rkmckenna To: dev@brooklyn.apache.org Reply-To: dev@brooklyn.apache.org References: In-Reply-To: Subject: [GitHub] brooklyn-server issue #753: Update jclouds to 2.0.2 Content-Type: text/plain Message-Id: <20170711142407.EFE1BE04AA@git1-us-west.apache.org> Date: Tue, 11 Jul 2017 14:24:07 +0000 (UTC) archived-at: Tue, 11 Jul 2017 14:24:10 -0000 Github user m4rkmckenna commented on the issue: https://github.com/apache/brooklyn-server/pull/753 Thanks @neykov ive tested the above with a simple application in the following locations - AWS - azure-arm - GCE - openstack - Softlayer --- 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. ---