Return-Path: X-Original-To: apmail-karaf-dev-archive@minotaur.apache.org Delivered-To: apmail-karaf-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 63B64177DE for ; Tue, 24 Mar 2015 10:52:57 +0000 (UTC) Received: (qmail 45522 invoked by uid 500); 24 Mar 2015 10:52:57 -0000 Delivered-To: apmail-karaf-dev-archive@karaf.apache.org Received: (qmail 45481 invoked by uid 500); 24 Mar 2015 10:52:57 -0000 Mailing-List: contact dev-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list dev@karaf.apache.org Delivered-To: moderator for dev@karaf.apache.org Received: (qmail 16508 invoked by uid 99); 24 Mar 2015 10:10:02 -0000 From: FlavioF To: dev@karaf.apache.org Reply-To: dev@karaf.apache.org Message-ID: Subject: [GitHub] karaf-cellar pull request: [KARAF-3628] Fixed Hazelcast Discovery ... Content-Type: text/plain Date: Tue, 24 Mar 2015 10:10:02 +0000 (UTC) GitHub user FlavioF opened a pull request: https://github.com/apache/karaf-cellar/pull/3 [KARAF-3628] Fixed Hazelcast Discovery Service when starting a new Hazelcast instance You can merge this pull request into a Git repository by running: $ git pull https://github.com/FlavioF/karaf-cellar fix_hazelcast_discovery_service Alternatively you can review and apply these changes as the patch at: https://github.com/apache/karaf-cellar/pull/3.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3 ---- commit 71332ef1a5741dabbd055a002ff87ca093d82e7d Author: Flávio Ferreira Date: 2015-03-20T17:13:02Z [KARAF-3628] Improved Hazelcast Discovery Service when starting a new Hazelcast instance ---- --- 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. ---