camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CAMEL-7777) GitHub component
Date Tue, 23 Sep 2014 20:44:34 GMT

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

Christian Müller 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/xml/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" from GitHub, as
well as produce "actions".  We're moving towards using Camel as 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 API 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 Mylyn and licensed under the EPL.  So, there shouldn't be any reason why
this would need to be restricted to Camel Extras.
> Similar to what I did for camel-twitter, the Exchange payloads would be the SDK-provided
objects themselves (PullRequest, CommitComment, RepositoryTag, RepositoryCommit, etc.)



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

Mime
View raw message