You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2019/08/19 10:27:08 UTC

[camel] 03/03: Added back original title for known issues and Camel-maven-plugin

This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git

commit 0343eb7a9a3fd632c33e50b35797d01c40edcc01
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Mon Aug 19 12:26:22 2019 +0200

    Added back original title for known issues and Camel-maven-plugin
---
 MIGRATION.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/MIGRATION.md b/MIGRATION.md
index fa73ec0..6e68b5b 100644
--- a/MIGRATION.md
+++ b/MIGRATION.md
@@ -524,7 +524,8 @@ The XMLSecurity data format has renamed the attribute `keyOrTrustStoreParameters
 The `<zipFile>` data format has been renamed to `<zipfile>`.
 
 
-### Migrating Camel Maven Plugins
+Migrating Camel Maven Plugins
+----------------------------
 
 The `camel-maven-plugin` has been split up into two maven plugins:
 
@@ -536,7 +537,8 @@ The former has the `run` goal, which is intended for quickly running Camel appli
 The `camel-report-maven-plugin` has the `validate` and `route-coverage` goals which is used for generating reports of your Camel projects such as validating Camel endpoint URIs and route coverage reports, etc.
 
 
-### Known Issues
+Known Issues
+----------------------------
 
 There is an issue with MDC logging and correctly transferring the Camel breadcrumb id's under certain situations with routing over asynchronous endpoints, due to the internal routing engine refactorings. This change also affects the `camel-zipkin` component, which may not correctly transfer the span id's when using MDC logging as well.