This is an automated email from the ASF dual-hosted git repository.
pascalschumacher pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new f735261 Some small improvements to the grammar of the Camel 3.7
upgrade guide.
f735261 is described below
commit f735261d75a296b1ed6baf5b947e9d2710fda368
Author: PascalSchumacher <pascalschumac...@gmx.net>
AuthorDate: Tue Jan 5 19:10:34 2021 +0100
Some small improvements to the grammar of the Camel 3.7 upgrade guide.
---
.../ROOT/pages/camel-3x-upgrade-guide-3_7.adoc | 64 +++++++++++-----------
1 file changed, 32 insertions(+), 32 deletions(-)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_7.adoc
b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_7.adoc
index ef6deb9..2758197 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_7.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_7.adoc
@@ -138,19 +138,19 @@ For each exchange now in the body you'll get the commit
full message as a String
Other information has been stored in headers declared in GitConstants class:
-- GIT_COMMIT_ID - "CamelGitCommitId" - The commit Id
-- GIT_COMMIT_AUTHOR_NAME - "CamelGitAuthorName" - The commit Author name
-- GIT_COMMIT_COMMITTER_NAME - "CamelGitCommiterName" - The commit committer
name
-- GIT_COMMIT_TIME - "CamelGitCommitTime" - The commit time
+* GIT_COMMIT_ID - "CamelGitCommitId" - The commit Id
+* GIT_COMMIT_AUTHOR_NAME - "CamelGitAuthorName" - The commit Author name
+* GIT_COMMIT_COMMITTER_NAME - "CamelGitCommiterName" - The commit committer
name
+* GIT_COMMIT_TIME - "CamelGitCommitTime" - The commit time
The Camel Git Branch consumer has been changed a bit.
For each exchange now in the body you'll get the branch ref name and not the
full ref like before.
-Other information has been stored in headers declared in GitConstants class:
+Other information has been stored in headers declared in `GitConstants` class:
-- GIT_BRANCH_LEAF - "CamelGitBranchLeaf" - Leaf
-- GIT_BRANCH_OBJECT_ID - "CamelGitBranchObjectId" - Object Id
+* GIT_BRANCH_LEAF - "CamelGitBranchLeaf" - Leaf
+* GIT_BRANCH_OBJECT_ID - "CamelGitBranchObjectId" - Object Id
The Camel Git Tag consumer has been changed a bit.
@@ -158,19 +158,19 @@ For each exchange now in the body you'll get the tag ref
name and not the full r
Other information has been stored in headers declared in GitConstants class:
-- GIT_TAG_LEAF - "CamelGitTagLeaf" - Leaf
-- GIT_TAG_OBJECT_ID - "CamelGitTagObjectId" - Object Id
+* GIT_TAG_LEAF - "CamelGitTagLeaf" - Leaf
+* GIT_TAG_OBJECT_ID - "CamelGitTagObjectId" - Object Id
=== camel-github
-Login using username and password is no longer supported by github and these
options has been removed
+Login using username and password is no longer supported by github and these
options have been removed
(https://developer.github.com/changes/2020-02-14-deprecating-password-auth/).
Login must be done using the `oauthToken` option.
=== Camel-AWS2-S3 Autowire support
-The camel-aws2-s3 now has support for autowiring the amazonS3Client option
with a S3Client instance coming from the registry.
+The camel-aws2-s3 component now has support for autowiring the amazonS3Client
option with a S3Client instance coming from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-S3 UseIamCredentials
@@ -179,78 +179,78 @@ The option useIamCredentials has been renamed to
useDefaultCredentialsProvider,
=== Camel-AWS2-Cloudwatch Autowire support
-The camel-aws2-cw now has support for autowiring the amazonCwClient option
with a CloudWatchClient instance coming from the registry.
+The camel-aws2-cw component now has support for autowiring the amazonCwClient
option with a CloudWatchClient instance coming from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-DDB Autowire support
-The camel-aws2-ddb now has support for autowiring the amazonDDBClient option
with a DynamoDbClient instance coming from the registry.
+The camel-aws2-ddb component now has support for autowiring the
amazonDDBClient option with a DynamoDbClient instance coming from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
-The camel-aws2-ddbstreams now has support for autowiring the
amazonDynamoDbStreamsClient option with a DynamoDbStreamsClient instance coming
from the registry.
+The camel-aws2-ddbstreams component now has support for autowiring the
amazonDynamoDbStreamsClient option with a DynamoDbStreamsClient instance coming
from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-EC2 Autowire support
-The camel-aws2-ec2 now has support for autowiring the amazonEc2Client option
with a Ec2Client instance coming from the registry.
+The camel-aws2-ec2 component now has support for autowiring the
amazonEc2Client option with an Ec2Client instance coming from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-ECS Autowire support
-The camel-aws2-ecs now has support for autowiring the ecsClient option with a
EcsClient instance coming from the registry.
+The camel-aws2-ecs component now has support for autowiring the ecsClient
option with an EcsClient instance coming from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-EKS Autowire support
-The camel-aws2-eks now has support for autowiring the eksClient option with a
EksClient instance coming from the registry.
+The camel-aws2-eks component now has support for autowiring the eksClient
option with an EksClient instance coming from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-Eventbridge Autowire support
-The camel-aws2-eventbridge now has support for autowiring the
eventBridgeClient option with a EventBridgeClient instance coming from the
registry.
+The camel-aws2-eventbridge component now has support for autowiring the
eventBridgeClient option with an EventBridgeClient instance coming from the
registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-IAM Autowire support
-The camel-aws2-iam now has support for autowiring the iamClient option with a
IamClient instance coming from the registry.
+The camel-aws2-iam component now has support for autowiring the iamClient
option with an IamClient instance coming from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-Kinesis Autowire support
-The camel-aws2-kinesis now has support for autowiring the amazonKinesisClient
option with a KinesisClient instance coming from the registry.
+The camel-aws2-kinesis component now has support for autowiring the
amazonKinesisClient option with a KinesisClient instance coming from the
registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
-The camel-aws2-kinesis-firehose now has support for autowiring the
amazonKinesisFirehoseClient option with a FirehoseClient instance coming from
the registry.
+The camel-aws2-kinesis-firehose component now has support for autowiring the
amazonKinesisFirehoseClient option with a FirehoseClient instance coming from
the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-KMS Autowire support
-The camel-aws2-kms now has support for autowiring the awsLambdaClient option
with a LambdaClient instance coming from the registry.
+The camel-aws2-kms component now has support for autowiring the
awsLambdaClient option with a LambdaClient instance coming from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-Lambda Autowire support
-The camel-aws2-kms now has support for autowiring the kmsClient option with a
KmsClient instance coming from the registry.
+The camel-aws2-kms component now has support for autowiring the kmsClient
option with a KmsClient instance coming from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-MQ Autowire support
-The camel-aws2-mq now has support for autowiring the amazonMqClient option
with a MqClient instance coming from the registry.
+The camel-aws2-mq component now has support for autowiring the amazonMqClient
option with a MqClient instance coming from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-MSK Autowire support
-The camel-aws2-msk now has support for autowiring the mskClient option with a
KafkaClient instance coming from the registry.
+The camel-aws2-msk component now has support for autowiring the mskClient
option with a KafkaClient instance coming from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-SES Autowire support
-The camel-aws2-ses now has support for autowiring the amazonSESClient option
with a SesClient instance coming from the registry.
+The camel-aws2-ses component now has support for autowiring the
amazonSESClient option with a SesClient instance coming from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-SNS Autowire support
-The camel-aws2-sns now has support for autowiring the amazonSNSClient option
with a SnsClient instance coming from the registry.
+The camel-aws2-sns component now has support for autowiring the
amazonSNSClient option with a SnsClient instance coming from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-SNS UseIamCredentials
@@ -259,7 +259,7 @@ The option useIamCredentials has been renamed to
useDefaultCredentialsProvider,
=== Camel-AWS2-SQS Autowire support
-The camel-aws2-sqs now has support for autowiring the amazonSQSClient option
with a SqsClient instance coming from the registry.
+The camel-aws2-sqs component now has support for autowiring the
amazonSQSClient option with a SqsClient instance coming from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-SQS UseIamCredentials
@@ -268,17 +268,17 @@ The option useIamCredentials has been renamed to
useDefaultCredentialsProvider,
=== Camel-AWS2-STS Autowire support
-The camel-aws2-sts now has support for autowiring the stsClient option with a
StsClient instance coming from the registry.
+The camel-aws2-sts component now has support for autowiring the stsClient
option with a StsClient instance coming from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-Translate Autowire support
-The camel-aws2-translate now has support for autowiring the translateClient
option with a TranslateClient instance coming from the registry.
+The camel-aws2-translate component now has support for autowiring the
translateClient option with a TranslateClient instance coming from the registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== Camel-AWS2-Athena Autowire support
-The camel-aws2-athena now has support for autowiring the amazonAthenaClient
option with a AthenaClient instance coming from the registry.
+The camel-aws2-athena component now has support for autowiring the
amazonAthenaClient option with an AthenaClient instance coming from the
registry.
In this context, it wasn't making sense to maintain the autodiscoverClient
option, which has been removed.
=== camel-salesforce
@@ -297,6 +297,6 @@ you may need to have a transformation that explicitly
converts spaces to "{plus}
The camel-google-bigquery component was updated to use the latest version of
`google-cloud-bigquery`. Some features of `GoogleBigQueryConnectionFactory` are
no longer supported.
-It is no longer possible to provide a the service account private key as a
String parameter to `GoogleBigQueryConnectionFactory`. Instead, you should use
`setCredentialsFileLocation` to
+It is no longer possible to provide the service account private key as a
String parameter to `GoogleBigQueryConnectionFactory`. Instead, you should use
`setCredentialsFileLocation` to
discover the private key from your credentials file. Or use the fallback
mechanism for discovering credentials by setting the
`GOOGLE_APPLICATION_CREDENTIALS` environment variable. Refer to the
component documentation for more information.
