Return-Path: X-Original-To: apmail-brooklyn-dev-archive@minotaur.apache.org Delivered-To: apmail-brooklyn-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8B38B17AB4 for ; Tue, 30 Sep 2014 08:14:08 +0000 (UTC) Received: (qmail 80162 invoked by uid 500); 30 Sep 2014 08:14:08 -0000 Delivered-To: apmail-brooklyn-dev-archive@brooklyn.apache.org Received: (qmail 80124 invoked by uid 500); 30 Sep 2014 08:14:08 -0000 Mailing-List: contact dev-help@brooklyn.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@brooklyn.incubator.apache.org Delivered-To: mailing list dev@brooklyn.incubator.apache.org Received: (qmail 80111 invoked by uid 99); 30 Sep 2014 08:14:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Sep 2014 08:14:08 +0000 X-ASF-Spam-Status: No, hits=-2000.6 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 30 Sep 2014 08:13:46 +0000 Received: (qmail 80015 invoked by uid 99); 30 Sep 2014 08:13:44 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Sep 2014 08:13:44 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id EF265A036DA; Tue, 30 Sep 2014 08:13:43 +0000 (UTC) From: alasdairhodge To: dev@brooklyn.incubator.apache.org Reply-To: dev@brooklyn.incubator.apache.org References: In-Reply-To: Subject: [GitHub] incubator-brooklyn pull request: Added install resources configura... Content-Type: text/plain Message-Id: <20140930081343.EF265A036DA@tyr.zones.apache.org> Date: Tue, 30 Sep 2014 08:13:43 +0000 (UTC) X-Virus-Checked: Checked by ClamAV on apache.org Github user alasdairhodge commented on the pull request: https://github.com/apache/incubator-brooklyn/pull/165#issuecomment-57280771 I see these mechanisms as primarily useful in blueprints (esp YAML) and not really intended for "internal" consumption within Java entity classes, mainly due to the difficulty in configuring custom resources simultaneously for a base entity and a subclass. Assuming this is the intended use-case, I think it's worth calling out explicitly in comments. --- 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. ---