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 56961200CCC for ; Fri, 21 Jul 2017 14:59:33 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 554C916D24E; Fri, 21 Jul 2017 12:59:33 +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 92CC116D24C for ; Fri, 21 Jul 2017 14:59:32 +0200 (CEST) Received: (qmail 25304 invoked by uid 500); 21 Jul 2017 12:59:31 -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 25293 invoked by uid 99); 21 Jul 2017 12:59:31 -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, 21 Jul 2017 12:59:31 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 6129ADFB94; Fri, 21 Jul 2017 12:59:31 +0000 (UTC) From: ahgittin To: dev@brooklyn.apache.org Reply-To: dev@brooklyn.apache.org References: In-Reply-To: Subject: [GitHub] brooklyn-server issue #772: Allow equivalent plans when replacing Content-Type: text/plain Message-Id: <20170721125931.6129ADFB94@git1-us-west.apache.org> Date: Fri, 21 Jul 2017 12:59:31 +0000 (UTC) archived-at: Fri, 21 Jul 2017 12:59:33 -0000 Github user ahgittin commented on the issue: https://github.com/apache/brooklyn-server/pull/772 Follow-up to #746 making it slightly more forgiving when replacing, should fix issues when dealing with complex catalogs/blueprints --- 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. ---