Return-Path: 
 <issues-return-19096-apmail-camel-issues-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-issues-archive@minotaur.apache.org
Delivered-To: apmail-camel-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 071A91151D
	for <apmail-camel-issues-archive@minotaur.apache.org>;
 Tue, 23 Sep 2014 20:44:37 +0000 (UTC)
Received: (qmail 47794 invoked by uid 500); 23 Sep 2014 20:44:34 -0000
Delivered-To: apmail-camel-issues-archive@camel.apache.org
Received: (qmail 47765 invoked by uid 500); 23 Sep 2014 20:44:34 -0000
Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@camel.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@camel.apache.org>
List-Post: <mailto:issues@camel.apache.org>
List-Id: <issues.camel.apache.org>
Reply-To: dev@camel.apache.org
Delivered-To: mailing list issues@camel.apache.org
Received: (qmail 47753 invoked by uid 99); 23 Sep 2014 20:44:34 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Sep 2014 20:44:34 +0000
Date: Tue, 23 Sep 2014 20:44:34 +0000 (UTC)
From: =?utf-8?Q?Christian_M=C3=BCller_=28JIRA=29?= <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12738910.1409777123000.106870.1411505074730@Atlassian.JIRA>
In-Reply-To: <JIRA.12738910.1409777123000@Atlassian.JIRA>
References: <JIRA.12738910.1409777123000@Atlassian.JIRA>
 <JIRA.12738910.1409777123517@arcas>
Subject: [jira] [Commented] (CAMEL-7777) GitHub component
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/CAMEL-7777?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1414=
5403#comment-14145403 ]=20

Christian M=C3=BCller commented on CAMEL-7777:
-----------------------------------------

At present, we cannot install the feature in Karaf 2.4.0:
{noformat}
christians-mbp:bin cmueller$ ./karaf clean
        __ __                  ____
       / //_/____ __________ _/ __/
      / ,<  / __ `/ ___/ __ `/ /_
     / /| |/ /_/ / /  / /_/ / __/
    /_/ |_|\__,_/_/   \__,_/_/

  Apache Karaf (2.4.0)

Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or type 'osgi:shutdown' or 'logout' to shutdown Karaf.

karaf@root> features:chooseurl camel 2.15-SNAPSHOT
Adding feature url mvn:org.apache.camel.karaf/apache-camel/2.15-SNAPSHOT/xm=
l/features
karaf@root> features:install camel-github
Error executing command: Error resolving artifact com.google.code.gson:gson=
:jar:2.2.0: Could not find artifact com.google.code.gson:gson:jar:2.2.0 in =
central (http://repo1.maven.org/maven2/)
karaf@root>
{noformat}

> GitHub component
> ----------------
>
>                 Key: CAMEL-7777
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7777
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Brett E. Meyer
>            Assignee: Willem Jiang
>             Fix For: 2.15.0
>
>
> For Overlord (http://projectoverlord.io), we need to consume "events" fro=
m GitHub, as well as produce "actions".  We're moving towards using Camel a=
s a backbone for various capabilities, and as such are writing the endpoint=
 functionality as new Camel components.  I'd love to see this incorporated =
as another mainline Camel component.
> Work in progress:
> https://github.com/brmeyer/camel-github
> Consumer ideas:
> github://pullRequest (new pull requests)
> github://pullRequestComment (new pull request comments)
> github://commit/[branch] (new commits)
> github://tag (new tags)
> Producer ideas:
> github://pullRequestComment/[pr #]
> Obviously, that's only a small portion of the capabilities.  The GitHub A=
PI is extensive and opens a large variety of possibilities.
> It uses the org.eclipse.egit.github.core SDK (https://github.com/eclipse/=
egit-github/tree/master/org.eclipse.egit.github.core), which is a part of M=
ylyn and licensed under the EPL.  So, there shouldn't be any reason why thi=
s would need to be restricted to Camel Extras.
> Similar to what I did for camel-twitter, the Exchange payloads would be t=
he SDK-provided objects themselves (PullRequest, CommitComment, RepositoryT=
ag, RepositoryCommit, etc.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)