[CAMEL-10798] camel-twitter, camel-ignite - Make the uri endpoints separated

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.20.0
• Estimated Complexity: Unknown
• Assignee: Tomohisa Igarashi
• Reporter: Claus Ibsen
• Created: 07/Feb/17 12:08
• Updated: 06/Jun/17 07:52
• Resolved: 06/Jun/17 07:52

Description

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.

Issue Links

• incorporates: CAMEL-11150 camel-ignite is removed from readme on each full build
• links to: GitHub Pull Request #1648
• links to: GitHub Pull Request #1657

Sub-Tasks

• Split camel-twitter component: Resolved
• Split camel-kubernetes component: Resolved
• Replace dummy URI paths on directmessage and search with something meaningful: Resolved