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 450AA200C64 for ; Fri, 28 Apr 2017 12:02:57 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 41FA2160BA3; Fri, 28 Apr 2017 10:02:57 +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 814C3160B8C for ; Fri, 28 Apr 2017 12:02:56 +0200 (CEST) Received: (qmail 98878 invoked by uid 500); 28 Apr 2017 10:02:55 -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 98867 invoked by uid 99); 28 Apr 2017 10:02:55 -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; Fri, 28 Apr 2017 10:02:55 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 61DEBE10BF; Fri, 28 Apr 2017 10:02:55 +0000 (UTC) From: geomacy To: dev@brooklyn.apache.org Reply-To: dev@brooklyn.apache.org References: In-Reply-To: Subject: [GitHub] brooklyn-server issue #645: Persist OSGi bundles Content-Type: text/plain Message-Id: <20170428100255.61DEBE10BF@git1-us-west.apache.org> Date: Fri, 28 Apr 2017 10:02:55 +0000 (UTC) archived-at: Fri, 28 Apr 2017 10:02:57 -0000 Github user geomacy commented on the issue: https://github.com/apache/brooklyn-server/pull/645 hi @ahgittin the `classpath://io.cloudsoft.cli44:plane.png` seems to work for me ![screen shot 2017-04-28 at 11 01 21](https://cloud.githubusercontent.com/assets/14142759/25524346/124431ca-2c02-11e7-84cb-5831eca2d7ef.png) but I agree that this is something that can be treated separately. Think this is good to merge and handle any issues subsequently. --- 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. ---