You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2016/08/16 08:03:47 UTC
[23/51] [partial] camel git commit: CAMEL-9541: Use -component as
suffix for component docs.
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-git/src/main/docs/git-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-git/src/main/docs/git-component.adoc b/components/camel-git/src/main/docs/git-component.adoc
new file mode 100644
index 0000000..e2e68b4
--- /dev/null
+++ b/components/camel-git/src/main/docs/git-component.adoc
@@ -0,0 +1,118 @@
+[[Git-GitComponent]]
+Git Component
+~~~~~~~~~~~~~
+
+*Available as of Camel 2.16*
+
+The�*git:*�component allows you to work with a generic Git repository.�
+
+[source,xml]
+------------------------------------------------------------
+<dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-git</artifactId>
+ <version>x.x.x</version>
+ <!-- use the same version as your Camel core version -->
+</dependency>
+------------------------------------------------------------
+
+*URI Format*
+
+[source,java]
+-----------------------------------
+git://localRepositoryPath[?options]
+-----------------------------------
+
+[[Git-URIOptions]]
+URI Options
+^^^^^^^^^^^
+
+The producer allows to do operations on a specific repository. +
+The consumer allows consuming commits, tags and branches on a specific
+repository.
+
+
+// component options: START
+The Git component has no options.
+// component options: END
+
+
+
+
+// endpoint options: START
+The Git component supports 13 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| localPath | common | | String | *Required* Local repository path
+| branchName | common | | String | The branch name to work on
+| password | common | | String | Remote repository password
+| remoteName | common | | String | The remote repository name to use in particular operation like pull
+| remotePath | common | | String | The remote repository path
+| tagName | common | | String | The tag name to work on
+| username | common | | String | Remote repository username
+| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| type | consumer | | GitType | The consumer type
+| exceptionHandler | consumer (advanced) | | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| operation | producer | | String | The operation to do on the repository
+| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
+| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
+|=======================================================================
+{% endraw %}
+// endpoint options: END
+
+
+
+
+[[Git-MessageHeaders]]
+Message Headers
+^^^^^^^^^^^^^^^
+
+[width="100%",cols="10%,10%,10%,20%,50%",options="header",]
+|=======================================================================
+|Name |Default Value |Type |Context |Description
+
+|CamelGitOperation |`null` |String |Producer |The operation to do on a repository, if not specified as endpoint option
+
+|CamelGitFilename |`null` |String |Producer |The file name in an add operation
+
+|CamelGitCommitMessage |`null` |String |Producer |The commit message related in a commit operation
+
+|CamelGitCommitUsername |`null` |String |Producer |The commit username in a commit operation
+
+|CamelGitCommitEmail |`null` |String |Producer |The commit email in a commit operation
+
+|CamelGitCommitId |`null` |String |Producer |The commit id
+|=======================================================================
+
+[[Git-ProducerExample]]
+Producer Example
+^^^^^^^^^^^^^^^^
+
+Below is an example route of a producer that add a file test.java to a
+local repository, commit it with a specific message on master branch and
+then push it to remote repository.
+
+[source,java]
+--------------------------------------------------------------------------------------------------------------------
+from("direct:start")
+ .setHeader(GitConstants.GIT_FILE_NAME, constant("test.java"))
+ .to("git:///tmp/testRepo?operation=add")
+ .setHeader(GitConstants.GIT_COMMIT_MESSAGE, constant("first commit"))
+ .to("git:///tmp/testRepo?operation=commit")
+ .to("git:///tmp/testRepo?operation=push&remotePath=https://foo.com/test/test.git&username=xxx&password=xxx")
+--------------------------------------------------------------------------------------------------------------------
+
+[[Git-ConsumerExample]]
+Consumer Example
+^^^^^^^^^^^^^^^^
+
+Below is an example route of a consumer that consumes commit:
+
+[source,java]
+---------------------------------------
+from("git:///tmp/testRepo?type=commit")
+ .to(....)
+---------------------------------------
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-git/src/main/docs/git.adoc
----------------------------------------------------------------------
diff --git a/components/camel-git/src/main/docs/git.adoc b/components/camel-git/src/main/docs/git.adoc
deleted file mode 100644
index e2e68b4..0000000
--- a/components/camel-git/src/main/docs/git.adoc
+++ /dev/null
@@ -1,118 +0,0 @@
-[[Git-GitComponent]]
-Git Component
-~~~~~~~~~~~~~
-
-*Available as of Camel 2.16*
-
-The�*git:*�component allows you to work with a generic Git repository.�
-
-[source,xml]
-------------------------------------------------------------
-<dependency>
- <groupId>org.apache.camel</groupId>
- <artifactId>camel-git</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-------------------------------------------------------------
-
-*URI Format*
-
-[source,java]
------------------------------------
-git://localRepositoryPath[?options]
------------------------------------
-
-[[Git-URIOptions]]
-URI Options
-^^^^^^^^^^^
-
-The producer allows to do operations on a specific repository. +
-The consumer allows consuming commits, tags and branches on a specific
-repository.
-
-
-// component options: START
-The Git component has no options.
-// component options: END
-
-
-
-
-// endpoint options: START
-The Git component supports 13 endpoint options which are listed below:
-
-{% raw %}
-[width="100%",cols="2s,1,1m,1m,5",options="header"]
-|=======================================================================
-| Name | Group | Default | Java Type | Description
-| localPath | common | | String | *Required* Local repository path
-| branchName | common | | String | The branch name to work on
-| password | common | | String | Remote repository password
-| remoteName | common | | String | The remote repository name to use in particular operation like pull
-| remotePath | common | | String | The remote repository path
-| tagName | common | | String | The tag name to work on
-| username | common | | String | Remote repository username
-| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| type | consumer | | GitType | The consumer type
-| exceptionHandler | consumer (advanced) | | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| operation | producer | | String | The operation to do on the repository
-| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
-| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
-|=======================================================================
-{% endraw %}
-// endpoint options: END
-
-
-
-
-[[Git-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
-
-[width="100%",cols="10%,10%,10%,20%,50%",options="header",]
-|=======================================================================
-|Name |Default Value |Type |Context |Description
-
-|CamelGitOperation |`null` |String |Producer |The operation to do on a repository, if not specified as endpoint option
-
-|CamelGitFilename |`null` |String |Producer |The file name in an add operation
-
-|CamelGitCommitMessage |`null` |String |Producer |The commit message related in a commit operation
-
-|CamelGitCommitUsername |`null` |String |Producer |The commit username in a commit operation
-
-|CamelGitCommitEmail |`null` |String |Producer |The commit email in a commit operation
-
-|CamelGitCommitId |`null` |String |Producer |The commit id
-|=======================================================================
-
-[[Git-ProducerExample]]
-Producer Example
-^^^^^^^^^^^^^^^^
-
-Below is an example route of a producer that add a file test.java to a
-local repository, commit it with a specific message on master branch and
-then push it to remote repository.
-
-[source,java]
---------------------------------------------------------------------------------------------------------------------
-from("direct:start")
- .setHeader(GitConstants.GIT_FILE_NAME, constant("test.java"))
- .to("git:///tmp/testRepo?operation=add")
- .setHeader(GitConstants.GIT_COMMIT_MESSAGE, constant("first commit"))
- .to("git:///tmp/testRepo?operation=commit")
- .to("git:///tmp/testRepo?operation=push&remotePath=https://foo.com/test/test.git&username=xxx&password=xxx")
---------------------------------------------------------------------------------------------------------------------
-
-[[Git-ConsumerExample]]
-Consumer Example
-^^^^^^^^^^^^^^^^
-
-Below is an example route of a consumer that consumes commit:
-
-[source,java]
----------------------------------------
-from("git:///tmp/testRepo?type=commit")
- .to(....)
----------------------------------------
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-github/src/main/docs/github-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-github/src/main/docs/github-component.adoc b/components/camel-github/src/main/docs/github-component.adoc
new file mode 100644
index 0000000..c4d41ba
--- /dev/null
+++ b/components/camel-github/src/main/docs/github-component.adoc
@@ -0,0 +1,122 @@
+[[GitHub-GitHub]]
+GitHub
+~~~~~~
+
+*Available as of Camel 2.15*
+
+The GitHub component interacts with the GitHub API by
+encapsulating�http://org.eclipse.egit.github.core[egit-github]. It
+currently provides polling for new pull requests, pull request comments,
+tags, and commits. �It is also able to produce comments on pull
+requests, as well as close the pull request entirely.
+
+Rather than webhooks, this endpoint relies on simple polling. Reasons
+include:
+
+* Concern for reliability/stability
+* The types of payloads we're polling aren't typically large (plus,
+paging is available in the API)
+* The need to support apps running somewhere not publicly accessible
+where a webhook would fail
+
+Note that the GitHub API is fairly expansive. �Therefore, this component
+could be easily expanded to provide additional interactions.
+
+Maven users will need to add the following dependency to their pom.xml
+for this component:
+
+[source,xml]
+-----------------------------------------
+<dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-github</artifactId>
+ <version>${camel-version}</version>
+</dependency>
+-----------------------------------------
+
+[[GitHub-URIformat]]
+URI format
+^^^^^^^^^^
+
+[source,text]
+---------------------------
+github://endpoint[?options]
+---------------------------
+
+[[GitHub-MandatoryOptions:]]
+Mandatory Options:
+^^^^^^^^^^^^^^^^^^
+
+Note that these can be configured directly through the endpoint.
+
+
+// component options: START
+The GitHub component has no options.
+// component options: END
+
+
+
+// endpoint options: START
+The GitHub component supports 14 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| type | common | | GitHubType | *Required* What git operation to execute
+| branchName | consumer | | String | Name of branch
+| oauthToken | common | | String | GitHub OAuth token required unless username & password are provided
+| password | common | | String | GitHub password required unless oauthToken is provided
+| repoName | common | | String | *Required* GitHub repository name
+| repoOwner | common | | String | *Required* GitHub repository owner (organization)
+| username | common | | String | GitHub username required unless oauthToken is provided
+| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| exceptionHandler | consumer (advanced) | | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| encoding | producer | | String | To use the given encoding when getting a git commit file
+| state | producer | | String | To set git commit status state
+| targetUrl | producer | | String | To set git commit status target url
+| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
+| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
+|=======================================================================
+{% endraw %}
+// endpoint options: END
+
+
+
+[[GitHub-ConsumerEndpoints:]]
+Consumer Endpoints:
+^^^^^^^^^^^^^^^^^^^
+
+[width="100%",cols="20%,20%,60%",options="header",]
+|=======================================================================
+|Endpoint |Context |Body Type
+
+|pullRequest |polling |org.eclipse.egit.github.core.PullRequest
+
+|pullRequestComment |polling |org.eclipse.egit.github.core.Comment (comment on the general pull
+request discussion) or org.eclipse.egit.github.core.CommitComment
+(inline comment on a pull request diff)
+
+|tag |polling |org.eclipse.egit.github.core.RepositoryTag
+
+|commit |polling |org.eclipse.egit.github.core.RepositoryCommit
+|=======================================================================
+
+[[GitHub-ProducerEndpoints:]]
+Producer Endpoints:
+^^^^^^^^^^^^^^^^^^^
+
+[width="100%",cols="20%,20%,60%",options="header",]
+|=======================================================================
+|Endpoint |Body |Message Headers
+
+|pullRequestComment |String (comment text) | - GitHubPullRequest (integer) (REQUIRED): Pull request number.
+
+- GitHubInResponseTo (integer): Required if responding to another inline
+comment on the pull request diff. If left off, a general comment on the
+pull request discussion is assumed.
+
+|closePullRequest |none | - GitHubPullRequest (integer) (REQUIRED): Pull request number.
+
+|createIssue (From Camel 2.18) |String (issue body text) | - GitHubIssueTitle (String) (REQUIRED): Issue Title.
+|=======================================================================
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-github/src/main/docs/github.adoc
----------------------------------------------------------------------
diff --git a/components/camel-github/src/main/docs/github.adoc b/components/camel-github/src/main/docs/github.adoc
deleted file mode 100644
index c4d41ba..0000000
--- a/components/camel-github/src/main/docs/github.adoc
+++ /dev/null
@@ -1,122 +0,0 @@
-[[GitHub-GitHub]]
-GitHub
-~~~~~~
-
-*Available as of Camel 2.15*
-
-The GitHub component interacts with the GitHub API by
-encapsulating�http://org.eclipse.egit.github.core[egit-github]. It
-currently provides polling for new pull requests, pull request comments,
-tags, and commits. �It is also able to produce comments on pull
-requests, as well as close the pull request entirely.
-
-Rather than webhooks, this endpoint relies on simple polling. Reasons
-include:
-
-* Concern for reliability/stability
-* The types of payloads we're polling aren't typically large (plus,
-paging is available in the API)
-* The need to support apps running somewhere not publicly accessible
-where a webhook would fail
-
-Note that the GitHub API is fairly expansive. �Therefore, this component
-could be easily expanded to provide additional interactions.
-
-Maven users will need to add the following dependency to their pom.xml
-for this component:
-
-[source,xml]
------------------------------------------
-<dependency>
- <groupId>org.apache.camel</groupId>
- <artifactId>camel-github</artifactId>
- <version>${camel-version}</version>
-</dependency>
------------------------------------------
-
-[[GitHub-URIformat]]
-URI format
-^^^^^^^^^^
-
-[source,text]
----------------------------
-github://endpoint[?options]
----------------------------
-
-[[GitHub-MandatoryOptions:]]
-Mandatory Options:
-^^^^^^^^^^^^^^^^^^
-
-Note that these can be configured directly through the endpoint.
-
-
-// component options: START
-The GitHub component has no options.
-// component options: END
-
-
-
-// endpoint options: START
-The GitHub component supports 14 endpoint options which are listed below:
-
-{% raw %}
-[width="100%",cols="2s,1,1m,1m,5",options="header"]
-|=======================================================================
-| Name | Group | Default | Java Type | Description
-| type | common | | GitHubType | *Required* What git operation to execute
-| branchName | consumer | | String | Name of branch
-| oauthToken | common | | String | GitHub OAuth token required unless username & password are provided
-| password | common | | String | GitHub password required unless oauthToken is provided
-| repoName | common | | String | *Required* GitHub repository name
-| repoOwner | common | | String | *Required* GitHub repository owner (organization)
-| username | common | | String | GitHub username required unless oauthToken is provided
-| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| exceptionHandler | consumer (advanced) | | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| encoding | producer | | String | To use the given encoding when getting a git commit file
-| state | producer | | String | To set git commit status state
-| targetUrl | producer | | String | To set git commit status target url
-| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
-| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
-|=======================================================================
-{% endraw %}
-// endpoint options: END
-
-
-
-[[GitHub-ConsumerEndpoints:]]
-Consumer Endpoints:
-^^^^^^^^^^^^^^^^^^^
-
-[width="100%",cols="20%,20%,60%",options="header",]
-|=======================================================================
-|Endpoint |Context |Body Type
-
-|pullRequest |polling |org.eclipse.egit.github.core.PullRequest
-
-|pullRequestComment |polling |org.eclipse.egit.github.core.Comment (comment on the general pull
-request discussion) or org.eclipse.egit.github.core.CommitComment
-(inline comment on a pull request diff)
-
-|tag |polling |org.eclipse.egit.github.core.RepositoryTag
-
-|commit |polling |org.eclipse.egit.github.core.RepositoryCommit
-|=======================================================================
-
-[[GitHub-ProducerEndpoints:]]
-Producer Endpoints:
-^^^^^^^^^^^^^^^^^^^
-
-[width="100%",cols="20%,20%,60%",options="header",]
-|=======================================================================
-|Endpoint |Body |Message Headers
-
-|pullRequestComment |String (comment text) | - GitHubPullRequest (integer) (REQUIRED): Pull request number.
-
-- GitHubInResponseTo (integer): Required if responding to another inline
-comment on the pull request diff. If left off, a general comment on the
-pull request discussion is assumed.
-
-|closePullRequest |none | - GitHubPullRequest (integer) (REQUIRED): Pull request number.
-
-|createIssue (From Camel 2.18) |String (issue body text) | - GitHubIssueTitle (String) (REQUIRED): Issue Title.
-|=======================================================================
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc b/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
new file mode 100644
index 0000000..88b87a2
--- /dev/null
+++ b/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
@@ -0,0 +1,174 @@
+[[GoogleCalendar-GoogleCalendarComponent]]
+GoogleCalendar Component
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+*Available as of Camel 2.15*
+
+[[GoogleCalendar-ComponentDescription]]
+Component Description
+^^^^^^^^^^^^^^^^^^^^^
+
+The Google Calendar component provides access
+to�http://google.com/calendar[Google Calendar]�via
+the�https://developers.google.com/google-apps/calendar/v3/reference/[Google
+Calendar Web APIs].
+
+Google Calendar uses
+the�https://developers.google.com/accounts/docs/OAuth2[OAuth 2.0
+protocol]�for authenticating a Google account and authorizing access to
+user data. Before you can use this component, you will need
+to�https://developers.google.com/google-apps/calendar/auth[create an
+account and generate OAuth credentials]. Credentials comprise of a
+clientId, clientSecret, and a refreshToken. A handy resource for
+generating a long-lived�refreshToken is
+the�https://developers.google.com/oauthplayground[OAuth playground].
+
+Maven users will need to add the following dependency to their pom.xml
+for this component:
+
+----------------------------------------------------------
+ <dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-google-calendar</artifactId>
+ <version>2.15.0</version>
+ </dependency>
+
+----------------------------------------------------------
+
+[[GoogleCalendar-options]]
+1. Google Calendar Options
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+
+
+// component options: START
+The Google Calendar component supports 13 options which are listed below.
+
+
+
+{% raw %}
+[width="100%",cols="2s,1m,8",options="header"]
+|=======================================================================
+| Name | Java Type | Description
+| configuration | GoogleCalendarConfiguration | To use the shared configuration. Properties of the shared configuration can also be set individually.
+| clientFactory | GoogleCalendarClientFactory | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleCalendarClientFactory
+| apiName | GoogleCalendarApiName | What kind of operation to perform
+| methodName | String | What sub operation to use for the selected operation
+| clientId | String | Client ID of the calendar application
+| emailAddress | String | The emailAddress of the Google Service Account.
+| clientSecret | String | Client secret of the calendar application
+| accessToken | String | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.
+| refreshToken | String | OAuth 2 refresh token. Using this the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.
+| applicationName | String | Google calendar application name. Example would be camel-google-calendar/1.0
+| scopes | List | Specifies the level of permissions you want a calendar application to have to a user account. See https://developers.google.com/google-apps/calendar/auth for more info.
+| p12FileName | String | The name of the p12 file which has the private key to use with the Google Service Account.
+| user | String | The email address of the user the application is trying to impersonate in the service account flow
+|=======================================================================
+{% endraw %}
+// component options: END
+
+
+
+
+
+
+
+// endpoint options: START
+The Google Calendar component supports 16 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| apiName | common | | GoogleCalendarApiName | *Required* What kind of operation to perform
+| methodName | common | | String | *Required* What sub operation to use for the selected operation
+| accessToken | common | | String | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.
+| applicationName | common | | String | Google calendar application name. Example would be camel-google-calendar/1.0
+| clientId | common | | String | Client ID of the calendar application
+| clientSecret | common | | String | Client secret of the calendar application
+| emailAddress | common | | String | The emailAddress of the Google Service Account.
+| inBody | common | | String | Sets the name of a parameter to be passed in the exchange In Body
+| p12FileName | common | | String | The name of the p12 file which has the private key to use with the Google Service Account.
+| refreshToken | common | | String | OAuth 2 refresh token. Using this the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.
+| scopes | common | https://www.googleapis.com/auth/calendar | List | Specifies the level of permissions you want a calendar application to have to a user account. See https://developers.google.com/google-apps/calendar/auth for more info.
+| user | common | | String | The email address of the user the application is trying to impersonate in the service account flow
+| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| exceptionHandler | consumer (advanced) | | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
+| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
+|=======================================================================
+{% endraw %}
+// endpoint options: END
+
+
+[[GoogleCalendar-URIFormat]]
+URI Format
+^^^^^^^^^^
+
+The GoogleCalendar Component uses the following URI format:
+
+------------------------------------------------------------
+ google-calendar://endpoint-prefix/endpoint?[options]
+
+------------------------------------------------------------
+
+Endpoint prefix can be one of:
+
+* acl
+* calendars
+* channels
+* colors
+* events
+* freebusy
+* list
+* settings
+
+[[GoogleCalendar-ProducerEndpoints]]
+Producer Endpoints
+^^^^^^^^^^^^^^^^^^
+
+Producer endpoints can use endpoint prefixes followed by endpoint names
+and associated options described next. A shorthand alias can be used for
+some endpoints. The endpoint URI MUST contain a prefix.
+
+Endpoint options that are not mandatory are denoted by []. When there
+are no mandatory options for an endpoint, one of the set of [] options
+MUST be provided. Producer endpoints can also use a special option
+*`inBody`* that in turn should contain the name of the endpoint option
+whose value will be contained in the Camel Exchange In message.
+
+Any of the endpoint options can be provided in either the endpoint URI,
+or dynamically in a message header. The message header name must be of
+the format `CamelGoogleCalendar.<option>`. Note that the `inBody` option
+overrides message header, i.e. the endpoint option `inBody=option` would
+override a `CamelGoogleCalendar.option` header.
+
+
+[[GoogleCalendar-ConsumerEndpoints]]
+Consumer Endpoints
+^^^^^^^^^^^^^^^^^^
+
+Any of the producer endpoints can be used as a consumer endpoint.
+Consumer endpoints can use
+http://camel.apache.org/polling-consumer.html#PollingConsumer-ScheduledPollConsumerOptions[Scheduled
+Poll Consumer Options] with a `consumer.` prefix to schedule endpoint
+invocation. Consumer endpoints that return an array or collection will
+generate one exchange per element, and their routes will be executed
+once for each exchange.
+
+[[GoogleCalendar-MessageHeaders]]
+Message Headers
+^^^^^^^^^^^^^^^
+
+Any URI option can be provided in a message header for producer
+endpoints with a `CamelGoogleCalendar.` prefix.
+
+[[GoogleCalendar-MessageBody]]
+Message Body
+^^^^^^^^^^^^
+
+All result message bodies utilize objects provided by the underlying
+APIs used by the GoogleCalendarComponent. Producer endpoints can specify
+the option name for incoming message body in the `inBody` endpoint URI
+parameter. For endpoints that return an array or collection, a consumer
+endpoint will map every element to distinct messages. � ��
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-google-calendar/src/main/docs/google-calendar.adoc
----------------------------------------------------------------------
diff --git a/components/camel-google-calendar/src/main/docs/google-calendar.adoc b/components/camel-google-calendar/src/main/docs/google-calendar.adoc
deleted file mode 100644
index 88b87a2..0000000
--- a/components/camel-google-calendar/src/main/docs/google-calendar.adoc
+++ /dev/null
@@ -1,174 +0,0 @@
-[[GoogleCalendar-GoogleCalendarComponent]]
-GoogleCalendar Component
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-*Available as of Camel 2.15*
-
-[[GoogleCalendar-ComponentDescription]]
-Component Description
-^^^^^^^^^^^^^^^^^^^^^
-
-The Google Calendar component provides access
-to�http://google.com/calendar[Google Calendar]�via
-the�https://developers.google.com/google-apps/calendar/v3/reference/[Google
-Calendar Web APIs].
-
-Google Calendar uses
-the�https://developers.google.com/accounts/docs/OAuth2[OAuth 2.0
-protocol]�for authenticating a Google account and authorizing access to
-user data. Before you can use this component, you will need
-to�https://developers.google.com/google-apps/calendar/auth[create an
-account and generate OAuth credentials]. Credentials comprise of a
-clientId, clientSecret, and a refreshToken. A handy resource for
-generating a long-lived�refreshToken is
-the�https://developers.google.com/oauthplayground[OAuth playground].
-
-Maven users will need to add the following dependency to their pom.xml
-for this component:
-
-----------------------------------------------------------
- <dependency>
- <groupId>org.apache.camel</groupId>
- <artifactId>camel-google-calendar</artifactId>
- <version>2.15.0</version>
- </dependency>
-
-----------------------------------------------------------
-
-[[GoogleCalendar-options]]
-1. Google Calendar Options
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-
-
-// component options: START
-The Google Calendar component supports 13 options which are listed below.
-
-
-
-{% raw %}
-[width="100%",cols="2s,1m,8",options="header"]
-|=======================================================================
-| Name | Java Type | Description
-| configuration | GoogleCalendarConfiguration | To use the shared configuration. Properties of the shared configuration can also be set individually.
-| clientFactory | GoogleCalendarClientFactory | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleCalendarClientFactory
-| apiName | GoogleCalendarApiName | What kind of operation to perform
-| methodName | String | What sub operation to use for the selected operation
-| clientId | String | Client ID of the calendar application
-| emailAddress | String | The emailAddress of the Google Service Account.
-| clientSecret | String | Client secret of the calendar application
-| accessToken | String | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.
-| refreshToken | String | OAuth 2 refresh token. Using this the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.
-| applicationName | String | Google calendar application name. Example would be camel-google-calendar/1.0
-| scopes | List | Specifies the level of permissions you want a calendar application to have to a user account. See https://developers.google.com/google-apps/calendar/auth for more info.
-| p12FileName | String | The name of the p12 file which has the private key to use with the Google Service Account.
-| user | String | The email address of the user the application is trying to impersonate in the service account flow
-|=======================================================================
-{% endraw %}
-// component options: END
-
-
-
-
-
-
-
-// endpoint options: START
-The Google Calendar component supports 16 endpoint options which are listed below:
-
-{% raw %}
-[width="100%",cols="2s,1,1m,1m,5",options="header"]
-|=======================================================================
-| Name | Group | Default | Java Type | Description
-| apiName | common | | GoogleCalendarApiName | *Required* What kind of operation to perform
-| methodName | common | | String | *Required* What sub operation to use for the selected operation
-| accessToken | common | | String | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.
-| applicationName | common | | String | Google calendar application name. Example would be camel-google-calendar/1.0
-| clientId | common | | String | Client ID of the calendar application
-| clientSecret | common | | String | Client secret of the calendar application
-| emailAddress | common | | String | The emailAddress of the Google Service Account.
-| inBody | common | | String | Sets the name of a parameter to be passed in the exchange In Body
-| p12FileName | common | | String | The name of the p12 file which has the private key to use with the Google Service Account.
-| refreshToken | common | | String | OAuth 2 refresh token. Using this the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.
-| scopes | common | https://www.googleapis.com/auth/calendar | List | Specifies the level of permissions you want a calendar application to have to a user account. See https://developers.google.com/google-apps/calendar/auth for more info.
-| user | common | | String | The email address of the user the application is trying to impersonate in the service account flow
-| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| exceptionHandler | consumer (advanced) | | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
-| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
-|=======================================================================
-{% endraw %}
-// endpoint options: END
-
-
-[[GoogleCalendar-URIFormat]]
-URI Format
-^^^^^^^^^^
-
-The GoogleCalendar Component uses the following URI format:
-
-------------------------------------------------------------
- google-calendar://endpoint-prefix/endpoint?[options]
-
-------------------------------------------------------------
-
-Endpoint prefix can be one of:
-
-* acl
-* calendars
-* channels
-* colors
-* events
-* freebusy
-* list
-* settings
-
-[[GoogleCalendar-ProducerEndpoints]]
-Producer Endpoints
-^^^^^^^^^^^^^^^^^^
-
-Producer endpoints can use endpoint prefixes followed by endpoint names
-and associated options described next. A shorthand alias can be used for
-some endpoints. The endpoint URI MUST contain a prefix.
-
-Endpoint options that are not mandatory are denoted by []. When there
-are no mandatory options for an endpoint, one of the set of [] options
-MUST be provided. Producer endpoints can also use a special option
-*`inBody`* that in turn should contain the name of the endpoint option
-whose value will be contained in the Camel Exchange In message.
-
-Any of the endpoint options can be provided in either the endpoint URI,
-or dynamically in a message header. The message header name must be of
-the format `CamelGoogleCalendar.<option>`. Note that the `inBody` option
-overrides message header, i.e. the endpoint option `inBody=option` would
-override a `CamelGoogleCalendar.option` header.
-
-
-[[GoogleCalendar-ConsumerEndpoints]]
-Consumer Endpoints
-^^^^^^^^^^^^^^^^^^
-
-Any of the producer endpoints can be used as a consumer endpoint.
-Consumer endpoints can use
-http://camel.apache.org/polling-consumer.html#PollingConsumer-ScheduledPollConsumerOptions[Scheduled
-Poll Consumer Options] with a `consumer.` prefix to schedule endpoint
-invocation. Consumer endpoints that return an array or collection will
-generate one exchange per element, and their routes will be executed
-once for each exchange.
-
-[[GoogleCalendar-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
-
-Any URI option can be provided in a message header for producer
-endpoints with a `CamelGoogleCalendar.` prefix.
-
-[[GoogleCalendar-MessageBody]]
-Message Body
-^^^^^^^^^^^^
-
-All result message bodies utilize objects provided by the underlying
-APIs used by the GoogleCalendarComponent. Producer endpoints can specify
-the option name for incoming message body in the `inBody` endpoint URI
-parameter. For endpoints that return an array or collection, a consumer
-endpoint will map every element to distinct messages. � ��
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-google-drive/src/main/docs/google-drive-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-google-drive/src/main/docs/google-drive-component.adoc b/components/camel-google-drive/src/main/docs/google-drive-component.adoc
new file mode 100644
index 0000000..faea67a
--- /dev/null
+++ b/components/camel-google-drive/src/main/docs/google-drive-component.adoc
@@ -0,0 +1,175 @@
+[[GoogleDrive-GoogleDriveComponent]]
+GoogleDrive Component
+~~~~~~~~~~~~~~~~~~~~~
+
+*Available as of Camel 2.14*
+
+The Google Drive component provides access to the
+http://drive.google.com[Google Drive file storage service] via the
+https://developers.google.com/drive/v2/reference[Google Drive Web APIs].
+
+Google Drive uses
+the�https://developers.google.com/accounts/docs/OAuth2[OAuth 2.0
+protocol]�for authenticating a Google account and authorizing access to
+user data. Before you can use this component, you will need to
+https://developers.google.com/drive/web/auth/web-server[create an
+account and generate OAuth credentials]. Credentials comprise of a
+clientId, clientSecret, and a refreshToken. A handy resource for
+generating a long-lived�refreshToken is the
+https://developers.google.com/oauthplayground[OAuth playground].
+
+Maven users will need to add the following dependency to their pom.xml
+for this component:
+
+-------------------------------------------------------
+ <dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-google-drive</artifactId>
+ <version>2.14-SNAPSHOT</version>
+ </dependency>
+
+-------------------------------------------------------
+
+[[GoogleDrive-URIFormat]]
+URI Format
+^^^^^^^^^^
+
+'''''
+
+The GoogleDrive Component uses the following URI format:
+
+---------------------------------------------------------
+ google-drive://endpoint-prefix/endpoint?[options]
+
+---------------------------------------------------------
+
+Endpoint prefix can be one of:
+
+* drive-about
+* drive-apps
+* drive-changes
+* drive-channels
+* drive-children
+* drive-comments
+* drive-files
+* drive-parents
+* drive-permissions
+* drive-properties
+* drive-realtime
+* drive-replies
+* drive-revisions
+
+[[GoogleDrive-GoogleDriveComponent.1]]
+GoogleDriveComponent
+^^^^^^^^^^^^^^^^^^^^
+
+
+
+
+// component options: START
+The Google Drive component supports 10 options which are listed below.
+
+
+
+{% raw %}
+[width="100%",cols="2s,1m,8",options="header"]
+|=======================================================================
+| Name | Java Type | Description
+| configuration | GoogleDriveConfiguration | To use the shared configuration. Properties of the shared configuration can also be set individually.
+| clientFactory | GoogleDriveClientFactory | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleDriveClientFactory
+| apiName | GoogleDriveApiName | What kind of operation to perform
+| methodName | String | What sub operation to use for the selected operation
+| clientId | String | Client ID of the drive application
+| clientSecret | String | Client secret of the drive application
+| accessToken | String | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.
+| refreshToken | String | OAuth 2 refresh token. Using this the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.
+| applicationName | String | Google drive application name. Example would be camel-google-drive/1.0
+| scopes | List | Specifies the level of permissions you want a drive application to have to a user account. See https://developers.google.com/drive/web/scopes for more info.
+|=======================================================================
+{% endraw %}
+// component options: END
+
+
+
+
+
+
+
+// endpoint options: START
+The Google Drive component supports 14 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| apiName | common | | GoogleDriveApiName | *Required* What kind of operation to perform
+| methodName | common | | String | *Required* What sub operation to use for the selected operation
+| accessToken | common | | String | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.
+| applicationName | common | | String | Google drive application name. Example would be camel-google-drive/1.0
+| clientFactory | common | | GoogleDriveClientFactory | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleDriveClientFactory
+| clientId | common | | String | Client ID of the drive application
+| clientSecret | common | | String | Client secret of the drive application
+| inBody | common | | String | Sets the name of a parameter to be passed in the exchange In Body
+| refreshToken | common | | String | OAuth 2 refresh token. Using this the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.
+| scopes | common | | List | Specifies the level of permissions you want a drive application to have to a user account. See https://developers.google.com/drive/web/scopes for more info.
+| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| exceptionHandler | consumer (advanced) | | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
+| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
+|=======================================================================
+{% endraw %}
+// endpoint options: END
+
+
+
+[[GoogleDrive-ProducerEndpoints]]
+Producer Endpoints
+^^^^^^^^^^^^^^^^^^
+
+Producer endpoints can use endpoint prefixes followed by endpoint names
+and associated options described next. A shorthand alias can be used for
+some endpoints. The endpoint URI MUST contain a prefix.
+
+Endpoint options that are not mandatory are denoted by []. When there
+are no mandatory options for an endpoint, one of the set of [] options
+MUST be provided. Producer endpoints can also use a special option
+*`inBody`* that in turn should contain the name of the endpoint option
+whose value will be contained in the Camel Exchange In message.
+
+Any of the endpoint options can be provided in either the endpoint URI,
+or dynamically in a message header. The message header name must be of
+the format `CamelGoogleDrive.<option>`. Note that the `inBody` option
+overrides message header, i.e. the endpoint option `inBody=option` would
+override a `CamelGoogleDrive.option` header.
+
+For more information on the endpoints and options see API documentation
+at:�https://developers.google.com/drive/v2/reference/[https://developers.google.com/drive/v2/reference/]
+
+[[GoogleDrive-ConsumerEndpoints]]
+Consumer Endpoints
+^^^^^^^^^^^^^^^^^^
+
+Any of the producer endpoints can be used as a consumer endpoint.
+Consumer endpoints can use
+http://camel.apache.org/polling-consumer.html#PollingConsumer-ScheduledPollConsumerOptions[Scheduled
+Poll Consumer Options] with a `consumer.` prefix to schedule endpoint
+invocation. Consumer endpoints that return an array or collection will
+generate one exchange per element, and their routes will be executed
+once for each exchange.
+
+[[GoogleDrive-MessageHeaders]]
+Message Headers
+^^^^^^^^^^^^^^^
+
+Any URI option can be provided in a message header for producer
+endpoints with a `CamelGoogleDrive.` prefix.
+
+[[GoogleDrive-MessageBody]]
+Message Body
+^^^^^^^^^^^^
+
+All result message bodies utilize objects provided by the underlying
+APIs used by the GoogleDriveComponent. Producer endpoints can specify
+the option name for incoming message body in the `inBody` endpoint URI
+parameter. For endpoints that return an array or collection, a consumer
+endpoint will map every element to distinct messages. � ��
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-google-drive/src/main/docs/google-drive.adoc
----------------------------------------------------------------------
diff --git a/components/camel-google-drive/src/main/docs/google-drive.adoc b/components/camel-google-drive/src/main/docs/google-drive.adoc
deleted file mode 100644
index faea67a..0000000
--- a/components/camel-google-drive/src/main/docs/google-drive.adoc
+++ /dev/null
@@ -1,175 +0,0 @@
-[[GoogleDrive-GoogleDriveComponent]]
-GoogleDrive Component
-~~~~~~~~~~~~~~~~~~~~~
-
-*Available as of Camel 2.14*
-
-The Google Drive component provides access to the
-http://drive.google.com[Google Drive file storage service] via the
-https://developers.google.com/drive/v2/reference[Google Drive Web APIs].
-
-Google Drive uses
-the�https://developers.google.com/accounts/docs/OAuth2[OAuth 2.0
-protocol]�for authenticating a Google account and authorizing access to
-user data. Before you can use this component, you will need to
-https://developers.google.com/drive/web/auth/web-server[create an
-account and generate OAuth credentials]. Credentials comprise of a
-clientId, clientSecret, and a refreshToken. A handy resource for
-generating a long-lived�refreshToken is the
-https://developers.google.com/oauthplayground[OAuth playground].
-
-Maven users will need to add the following dependency to their pom.xml
-for this component:
-
--------------------------------------------------------
- <dependency>
- <groupId>org.apache.camel</groupId>
- <artifactId>camel-google-drive</artifactId>
- <version>2.14-SNAPSHOT</version>
- </dependency>
-
--------------------------------------------------------
-
-[[GoogleDrive-URIFormat]]
-URI Format
-^^^^^^^^^^
-
-'''''
-
-The GoogleDrive Component uses the following URI format:
-
----------------------------------------------------------
- google-drive://endpoint-prefix/endpoint?[options]
-
----------------------------------------------------------
-
-Endpoint prefix can be one of:
-
-* drive-about
-* drive-apps
-* drive-changes
-* drive-channels
-* drive-children
-* drive-comments
-* drive-files
-* drive-parents
-* drive-permissions
-* drive-properties
-* drive-realtime
-* drive-replies
-* drive-revisions
-
-[[GoogleDrive-GoogleDriveComponent.1]]
-GoogleDriveComponent
-^^^^^^^^^^^^^^^^^^^^
-
-
-
-
-// component options: START
-The Google Drive component supports 10 options which are listed below.
-
-
-
-{% raw %}
-[width="100%",cols="2s,1m,8",options="header"]
-|=======================================================================
-| Name | Java Type | Description
-| configuration | GoogleDriveConfiguration | To use the shared configuration. Properties of the shared configuration can also be set individually.
-| clientFactory | GoogleDriveClientFactory | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleDriveClientFactory
-| apiName | GoogleDriveApiName | What kind of operation to perform
-| methodName | String | What sub operation to use for the selected operation
-| clientId | String | Client ID of the drive application
-| clientSecret | String | Client secret of the drive application
-| accessToken | String | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.
-| refreshToken | String | OAuth 2 refresh token. Using this the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.
-| applicationName | String | Google drive application name. Example would be camel-google-drive/1.0
-| scopes | List | Specifies the level of permissions you want a drive application to have to a user account. See https://developers.google.com/drive/web/scopes for more info.
-|=======================================================================
-{% endraw %}
-// component options: END
-
-
-
-
-
-
-
-// endpoint options: START
-The Google Drive component supports 14 endpoint options which are listed below:
-
-{% raw %}
-[width="100%",cols="2s,1,1m,1m,5",options="header"]
-|=======================================================================
-| Name | Group | Default | Java Type | Description
-| apiName | common | | GoogleDriveApiName | *Required* What kind of operation to perform
-| methodName | common | | String | *Required* What sub operation to use for the selected operation
-| accessToken | common | | String | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.
-| applicationName | common | | String | Google drive application name. Example would be camel-google-drive/1.0
-| clientFactory | common | | GoogleDriveClientFactory | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleDriveClientFactory
-| clientId | common | | String | Client ID of the drive application
-| clientSecret | common | | String | Client secret of the drive application
-| inBody | common | | String | Sets the name of a parameter to be passed in the exchange In Body
-| refreshToken | common | | String | OAuth 2 refresh token. Using this the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.
-| scopes | common | | List | Specifies the level of permissions you want a drive application to have to a user account. See https://developers.google.com/drive/web/scopes for more info.
-| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| exceptionHandler | consumer (advanced) | | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
-| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
-|=======================================================================
-{% endraw %}
-// endpoint options: END
-
-
-
-[[GoogleDrive-ProducerEndpoints]]
-Producer Endpoints
-^^^^^^^^^^^^^^^^^^
-
-Producer endpoints can use endpoint prefixes followed by endpoint names
-and associated options described next. A shorthand alias can be used for
-some endpoints. The endpoint URI MUST contain a prefix.
-
-Endpoint options that are not mandatory are denoted by []. When there
-are no mandatory options for an endpoint, one of the set of [] options
-MUST be provided. Producer endpoints can also use a special option
-*`inBody`* that in turn should contain the name of the endpoint option
-whose value will be contained in the Camel Exchange In message.
-
-Any of the endpoint options can be provided in either the endpoint URI,
-or dynamically in a message header. The message header name must be of
-the format `CamelGoogleDrive.<option>`. Note that the `inBody` option
-overrides message header, i.e. the endpoint option `inBody=option` would
-override a `CamelGoogleDrive.option` header.
-
-For more information on the endpoints and options see API documentation
-at:�https://developers.google.com/drive/v2/reference/[https://developers.google.com/drive/v2/reference/]
-
-[[GoogleDrive-ConsumerEndpoints]]
-Consumer Endpoints
-^^^^^^^^^^^^^^^^^^
-
-Any of the producer endpoints can be used as a consumer endpoint.
-Consumer endpoints can use
-http://camel.apache.org/polling-consumer.html#PollingConsumer-ScheduledPollConsumerOptions[Scheduled
-Poll Consumer Options] with a `consumer.` prefix to schedule endpoint
-invocation. Consumer endpoints that return an array or collection will
-generate one exchange per element, and their routes will be executed
-once for each exchange.
-
-[[GoogleDrive-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
-
-Any URI option can be provided in a message header for producer
-endpoints with a `CamelGoogleDrive.` prefix.
-
-[[GoogleDrive-MessageBody]]
-Message Body
-^^^^^^^^^^^^
-
-All result message bodies utilize objects provided by the underlying
-APIs used by the GoogleDriveComponent. Producer endpoints can specify
-the option name for incoming message body in the `inBody` endpoint URI
-parameter. For endpoints that return an array or collection, a consumer
-endpoint will map every element to distinct messages. � ��
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-google-mail/src/main/docs/google-mail-component.adoc
----------------------------------------------------------------------
diff --git a/components/camel-google-mail/src/main/docs/google-mail-component.adoc b/components/camel-google-mail/src/main/docs/google-mail-component.adoc
new file mode 100644
index 0000000..dcf6af5
--- /dev/null
+++ b/components/camel-google-mail/src/main/docs/google-mail-component.adoc
@@ -0,0 +1,170 @@
+[[GoogleMail-GoogleMailComponent]]
+GoogleMail Component
+~~~~~~~~~~~~~~~~~~~~
+
+*Available as of Camel 2.15*
+
+[[GoogleMail-ComponentDescription]]
+Component Description
+^^^^^^^^^^^^^^^^^^^^^
+
+The Google Mail component provides access
+to�http://gmail.com/[Gmail]�via
+the�https://developers.google.com/gmail/api/v1/reference/[Google Mail
+Web APIs].
+
+Google Mail uses
+the�https://developers.google.com/accounts/docs/OAuth2[OAuth 2.0
+protocol]�for authenticating a Google account and authorizing access to
+user data. Before you can use this component, you will need
+to�https://developers.google.com/gmail/api/auth/web-server[create an
+account and generate OAuth credentials]. Credentials comprise of a
+clientId, clientSecret, and a refreshToken. A handy resource for
+generating a long-lived�refreshToken is
+the�https://developers.google.com/oauthplayground[OAuth playground].
+
+Maven users will need to add the following dependency to their pom.xml
+for this component:
+
+------------------------------------------------------
+ <dependency>
+ <groupId>org.apache.camel</groupId>
+ <artifactId>camel-google-mail</artifactId>
+ <version>2.15-SNAPSHOT</version>
+ </dependency>
+
+------------------------------------------------------
+
+[[GoogleMail-URIFormat]]
+URI Format
+^^^^^^^^^^
+
+The GoogleMail Component uses the following URI format:
+
+--------------------------------------------------------
+ google-mail://endpoint-prefix/endpoint?[options]
+
+--------------------------------------------------------
+
+Endpoint prefix can be one of:
+
+* attachments
+* drafts
+* history
+* labels
+* messages
+* threads
+* users
+
+[[GoogleMail-GoogleMailComponent.1]]
+GoogleMailComponent
+^^^^^^^^^^^^^^^^^^^
+
+
+
+
+// component options: START
+The Google Mail component supports 10 options which are listed below.
+
+
+
+{% raw %}
+[width="100%",cols="2s,1m,8",options="header"]
+|=======================================================================
+| Name | Java Type | Description
+| configuration | GoogleMailConfiguration | To use the shared configuration. Properties of the shared configuration can also be set individually.
+| clientFactory | GoogleMailClientFactory | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleMailClientFactory
+| apiName | GoogleMailApiName | What kind of operation to perform
+| methodName | String | What sub operation to use for the selected operation
+| clientId | String | Client ID of the mail application
+| clientSecret | String | Client secret of the mail application
+| accessToken | String | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.
+| refreshToken | String | OAuth 2 refresh token. Using this the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.
+| applicationName | String | Google mail application name. Example would be camel-google-mail/1.0
+| scopes | List | Specifies the level of permissions you want a mail application to have to a user account. See https://developers.google.com/gmail/api/auth/scopes for more info.
+|=======================================================================
+{% endraw %}
+// component options: END
+
+
+
+
+
+
+// endpoint options: START
+The Google Mail component supports 13 endpoint options which are listed below:
+
+{% raw %}
+[width="100%",cols="2s,1,1m,1m,5",options="header"]
+|=======================================================================
+| Name | Group | Default | Java Type | Description
+| apiName | common | | GoogleMailApiName | *Required* What kind of operation to perform
+| methodName | common | | String | *Required* What sub operation to use for the selected operation
+| accessToken | common | | String | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.
+| applicationName | common | | String | Google mail application name. Example would be camel-google-mail/1.0
+| clientId | common | | String | Client ID of the mail application
+| clientSecret | common | | String | Client secret of the mail application
+| inBody | common | | String | Sets the name of a parameter to be passed in the exchange In Body
+| refreshToken | common | | String | OAuth 2 refresh token. Using this the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.
+| scopes | common | | List | Specifies the level of permissions you want a mail application to have to a user account. See https://developers.google.com/gmail/api/auth/scopes for more info.
+| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| exceptionHandler | consumer (advanced) | | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
+| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
+| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
+|=======================================================================
+{% endraw %}
+// endpoint options: END
+
+
+
+[[GoogleMail-ProducerEndpoints]]
+Producer Endpoints
+^^^^^^^^^^^^^^^^^^
+
+Producer endpoints can use endpoint prefixes followed by endpoint names
+and associated options described next. A shorthand alias can be used for
+some endpoints. The endpoint URI MUST contain a prefix.
+
+Endpoint options that are not mandatory are denoted by []. When there
+are no mandatory options for an endpoint, one of the set of [] options
+MUST be provided. Producer endpoints can also use a special option
+*`inBody`* that in turn should contain the name of the endpoint option
+whose value will be contained in the Camel Exchange In message.
+
+Any of the endpoint options can be provided in either the endpoint URI,
+or dynamically in a message header. The message header name must be of
+the format `CamelGoogleMail.<option>`. Note that the `inBody` option
+overrides message header, i.e. the endpoint option `inBody=option` would
+override a `CamelGoogleMail.option` header.
+
+For more information on the endpoints and options see API documentation
+at:�https://developers.google.com/gmail/api/v1/reference/[https://developers.google.com/gmail/api/v1/reference/]
+
+[[GoogleMail-ConsumerEndpoints]]
+Consumer Endpoints
+^^^^^^^^^^^^^^^^^^
+
+Any of the producer endpoints can be used as a consumer endpoint.
+Consumer endpoints can use
+http://camel.apache.org/polling-consumer.html#PollingConsumer-ScheduledPollConsumerOptions[Scheduled
+Poll Consumer Options] with a `consumer.` prefix to schedule endpoint
+invocation. Consumer endpoints that return an array or collection will
+generate one exchange per element, and their routes will be executed
+once for each exchange.
+
+[[GoogleMail-MessageHeaders]]
+Message Headers
+^^^^^^^^^^^^^^^
+
+Any URI option can be provided in a message header for producer
+endpoints with a `CamelGoogleMail.` prefix.
+
+[[GoogleMail-MessageBody]]
+Message Body
+^^^^^^^^^^^^
+
+All result message bodies utilize objects provided by the underlying
+APIs used by the GoogleMailComponent. Producer endpoints can specify the
+option name for incoming message body in the `inBody` endpoint URI
+parameter. For endpoints that return an array or collection, a consumer
+endpoint will map every element to distinct messages. � ��
http://git-wip-us.apache.org/repos/asf/camel/blob/9c0b7baf/components/camel-google-mail/src/main/docs/google-mail.adoc
----------------------------------------------------------------------
diff --git a/components/camel-google-mail/src/main/docs/google-mail.adoc b/components/camel-google-mail/src/main/docs/google-mail.adoc
deleted file mode 100644
index dcf6af5..0000000
--- a/components/camel-google-mail/src/main/docs/google-mail.adoc
+++ /dev/null
@@ -1,170 +0,0 @@
-[[GoogleMail-GoogleMailComponent]]
-GoogleMail Component
-~~~~~~~~~~~~~~~~~~~~
-
-*Available as of Camel 2.15*
-
-[[GoogleMail-ComponentDescription]]
-Component Description
-^^^^^^^^^^^^^^^^^^^^^
-
-The Google Mail component provides access
-to�http://gmail.com/[Gmail]�via
-the�https://developers.google.com/gmail/api/v1/reference/[Google Mail
-Web APIs].
-
-Google Mail uses
-the�https://developers.google.com/accounts/docs/OAuth2[OAuth 2.0
-protocol]�for authenticating a Google account and authorizing access to
-user data. Before you can use this component, you will need
-to�https://developers.google.com/gmail/api/auth/web-server[create an
-account and generate OAuth credentials]. Credentials comprise of a
-clientId, clientSecret, and a refreshToken. A handy resource for
-generating a long-lived�refreshToken is
-the�https://developers.google.com/oauthplayground[OAuth playground].
-
-Maven users will need to add the following dependency to their pom.xml
-for this component:
-
-------------------------------------------------------
- <dependency>
- <groupId>org.apache.camel</groupId>
- <artifactId>camel-google-mail</artifactId>
- <version>2.15-SNAPSHOT</version>
- </dependency>
-
-------------------------------------------------------
-
-[[GoogleMail-URIFormat]]
-URI Format
-^^^^^^^^^^
-
-The GoogleMail Component uses the following URI format:
-
---------------------------------------------------------
- google-mail://endpoint-prefix/endpoint?[options]
-
---------------------------------------------------------
-
-Endpoint prefix can be one of:
-
-* attachments
-* drafts
-* history
-* labels
-* messages
-* threads
-* users
-
-[[GoogleMail-GoogleMailComponent.1]]
-GoogleMailComponent
-^^^^^^^^^^^^^^^^^^^
-
-
-
-
-// component options: START
-The Google Mail component supports 10 options which are listed below.
-
-
-
-{% raw %}
-[width="100%",cols="2s,1m,8",options="header"]
-|=======================================================================
-| Name | Java Type | Description
-| configuration | GoogleMailConfiguration | To use the shared configuration. Properties of the shared configuration can also be set individually.
-| clientFactory | GoogleMailClientFactory | To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleMailClientFactory
-| apiName | GoogleMailApiName | What kind of operation to perform
-| methodName | String | What sub operation to use for the selected operation
-| clientId | String | Client ID of the mail application
-| clientSecret | String | Client secret of the mail application
-| accessToken | String | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.
-| refreshToken | String | OAuth 2 refresh token. Using this the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.
-| applicationName | String | Google mail application name. Example would be camel-google-mail/1.0
-| scopes | List | Specifies the level of permissions you want a mail application to have to a user account. See https://developers.google.com/gmail/api/auth/scopes for more info.
-|=======================================================================
-{% endraw %}
-// component options: END
-
-
-
-
-
-
-// endpoint options: START
-The Google Mail component supports 13 endpoint options which are listed below:
-
-{% raw %}
-[width="100%",cols="2s,1,1m,1m,5",options="header"]
-|=======================================================================
-| Name | Group | Default | Java Type | Description
-| apiName | common | | GoogleMailApiName | *Required* What kind of operation to perform
-| methodName | common | | String | *Required* What sub operation to use for the selected operation
-| accessToken | common | | String | OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.
-| applicationName | common | | String | Google mail application name. Example would be camel-google-mail/1.0
-| clientId | common | | String | Client ID of the mail application
-| clientSecret | common | | String | Client secret of the mail application
-| inBody | common | | String | Sets the name of a parameter to be passed in the exchange In Body
-| refreshToken | common | | String | OAuth 2 refresh token. Using this the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.
-| scopes | common | | List | Specifies the level of permissions you want a mail application to have to a user account. See https://developers.google.com/gmail/api/auth/scopes for more info.
-| bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| exceptionHandler | consumer (advanced) | | ExceptionHandler | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions that will be logged at WARN/ERROR level and ignored.
-| exchangePattern | advanced | InOnly | ExchangePattern | Sets the default exchange pattern when creating an exchange
-| synchronous | advanced | false | boolean | Sets whether synchronous processing should be strictly used or Camel is allowed to use asynchronous processing (if supported).
-|=======================================================================
-{% endraw %}
-// endpoint options: END
-
-
-
-[[GoogleMail-ProducerEndpoints]]
-Producer Endpoints
-^^^^^^^^^^^^^^^^^^
-
-Producer endpoints can use endpoint prefixes followed by endpoint names
-and associated options described next. A shorthand alias can be used for
-some endpoints. The endpoint URI MUST contain a prefix.
-
-Endpoint options that are not mandatory are denoted by []. When there
-are no mandatory options for an endpoint, one of the set of [] options
-MUST be provided. Producer endpoints can also use a special option
-*`inBody`* that in turn should contain the name of the endpoint option
-whose value will be contained in the Camel Exchange In message.
-
-Any of the endpoint options can be provided in either the endpoint URI,
-or dynamically in a message header. The message header name must be of
-the format `CamelGoogleMail.<option>`. Note that the `inBody` option
-overrides message header, i.e. the endpoint option `inBody=option` would
-override a `CamelGoogleMail.option` header.
-
-For more information on the endpoints and options see API documentation
-at:�https://developers.google.com/gmail/api/v1/reference/[https://developers.google.com/gmail/api/v1/reference/]
-
-[[GoogleMail-ConsumerEndpoints]]
-Consumer Endpoints
-^^^^^^^^^^^^^^^^^^
-
-Any of the producer endpoints can be used as a consumer endpoint.
-Consumer endpoints can use
-http://camel.apache.org/polling-consumer.html#PollingConsumer-ScheduledPollConsumerOptions[Scheduled
-Poll Consumer Options] with a `consumer.` prefix to schedule endpoint
-invocation. Consumer endpoints that return an array or collection will
-generate one exchange per element, and their routes will be executed
-once for each exchange.
-
-[[GoogleMail-MessageHeaders]]
-Message Headers
-^^^^^^^^^^^^^^^
-
-Any URI option can be provided in a message header for producer
-endpoints with a `CamelGoogleMail.` prefix.
-
-[[GoogleMail-MessageBody]]
-Message Body
-^^^^^^^^^^^^
-
-All result message bodies utilize objects provided by the underlying
-APIs used by the GoogleMailComponent. Producer endpoints can specify the
-option name for incoming message body in the `inBody` endpoint URI
-parameter. For endpoints that return an array or collection, a consumer
-endpoint will map every element to distinct messages. � ��