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 9094C200C1A for ; Mon, 13 Feb 2017 15:45:19 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 8F1A2160B60; Mon, 13 Feb 2017 14:45:19 +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 D1C6D160B4D for ; Mon, 13 Feb 2017 15:45:18 +0100 (CET) Received: (qmail 62918 invoked by uid 500); 13 Feb 2017 14:45:18 -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 62907 invoked by uid 99); 13 Feb 2017 14:45:17 -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; Mon, 13 Feb 2017 14:45:17 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id AFAC8DFC31; Mon, 13 Feb 2017 14:45:17 +0000 (UTC) From: geomacy To: dev@brooklyn.apache.org Reply-To: dev@brooklyn.apache.org References: In-Reply-To: Subject: [GitHub] brooklyn-server issue #551: BROOKLYN-421: Adds DSL for $brooklyn:urlEncode(.... Content-Type: text/plain Message-Id: <20170213144517.AFAC8DFC31@git1-us-west.apache.org> Date: Mon, 13 Feb 2017 14:45:17 +0000 (UTC) archived-at: Mon, 13 Feb 2017 14:45:19 -0000 Github user geomacy commented on the issue: https://github.com/apache/brooklyn-server/pull/551 Actually I take it back - having looked more carefully at the spec for that j.n.URI constructor I think the above is a perfectly valid use. --- 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. ---