Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3614B18948 for ; Fri, 15 Jan 2016 14:15:34 +0000 (UTC) Received: (qmail 18696 invoked by uid 500); 15 Jan 2016 14:15:34 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 18649 invoked by uid 500); 15 Jan 2016 14:15:34 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 18638 invoked by uid 99); 15 Jan 2016 14:15:33 -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, 15 Jan 2016 14:15:33 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 7C141DFE13; Fri, 15 Jan 2016 14:15:33 +0000 (UTC) From: astefanutti To: dev@camel.apache.org Reply-To: dev@camel.apache.org Message-ID: Subject: [GitHub] camel pull request: Avoid non-static nested class and fix CS error Content-Type: text/plain Date: Fri, 15 Jan 2016 14:15:33 +0000 (UTC) GitHub user astefanutti opened a pull request: https://github.com/apache/camel/pull/776 Avoid non-static nested class and fix CS error You can merge this pull request into a Git repository by running: $ git pull https://github.com/astefanutti/camel CAMEL-9330 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/776.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 #776 ---- commit 501185d23b1c68676fc7e4709270208ab29ab2f3 Author: Antonin Stefanutti Date: 2016-01-15T14:14:50Z Avoid non-static nested class and fix CS error ---- --- 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. ---