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 695D5200C7F for ; Wed, 24 May 2017 21:16:57 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 67FFE160BB6; Wed, 24 May 2017 19:16: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 A6484160BA5 for ; Wed, 24 May 2017 21:16:56 +0200 (CEST) Received: (qmail 98803 invoked by uid 500); 24 May 2017 19:16:55 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 98792 invoked by uid 99); 24 May 2017 19:16: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; Wed, 24 May 2017 19:16:55 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 5EC73DFC2E; Wed, 24 May 2017 19:16:55 +0000 (UTC) From: clebertsuconic To: dev@activemq.apache.org Reply-To: dev@activemq.apache.org References: In-Reply-To: Subject: [GitHub] activemq-artemis issue #1288: ARTEMIS-1179: Add Optional Client JMS Destinat... Content-Type: text/plain Message-Id: <20170524191655.5EC73DFC2E@git1-us-west.apache.org> Date: Wed, 24 May 2017 19:16:55 +0000 (UTC) archived-at: Wed, 24 May 2017 19:16:57 -0000 Github user clebertsuconic commented on the issue: https://github.com/apache/activemq-artemis/pull/1288 Last time I checked there was a test failure on the unit tests.. something easy to be fixed. --- 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. ---