[
https://issues.apache.org/jira/browse/CAMEL-10798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982389#comment-15982389
]
ASF GitHub Bot commented on CAMEL-10798:
----------------------------------------
GitHub user igarashitm opened a pull request:
https://github.com/apache/camel/pull/1657
CAMEL-10798 Splitted hazelcast component into 11 which correspond to …
…each of endpoints
For post 2.19 release
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/igarashitm/camel CAMEL-10798-hazelcast
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1657.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 #1657
----
commit 91e7a0a6bb53426b859c5933643f21220321f12f
Author: Tomohisa Igarashi <tm.igara...@gmail.com>
Date: 2017-04-24T14:26:02Z
CAMEL-10798 Splitted hazelcast component into 11 which correspond to each
of endpoints
----
> camel-twitter, camel-ignite - Make the uri endpoints separated
> --------------------------------------------------------------
>
> Key: CAMEL-10798
> URL: https://issues.apache.org/jira/browse/CAMEL-10798
> Project: Camel
> Issue Type: Improvement
> Reporter: Claus Ibsen
> Assignee: Tomohisa Igarashi
> Fix For: Future
>
>
> They currently have the same @UriEndpoint that represents all of their
> possible endpoint combinations. This usually works fine for Camel components.
> But some components such as twitter, ignite, hazelcast etc do have to many
> different endpoints that have very specific options per different endpoint.
> We should split up this in different components so they are separated.
> So we have
> twitter-status
> twitter-search
> twitter-direct
> Or something.
> This will also help tooling, documentation, et all so they are clearly
> separated and there are no confusion. For example twitter mention do not
> support the delay option which only twitter search uses etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
