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:06 UTC

[camel] 01/03: Migration guide: Tracer has been implemented

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 60e593e5a6a8128d2e800f4f9dcb235da19376af
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Mon Aug 19 12:24:00 2019 +0200

    Migration guide: Tracer has been implemented
---
 MIGRATION.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/MIGRATION.md b/MIGRATION.md
index 1c0f87b..e7a0f51 100644
--- a/MIGRATION.md
+++ b/MIGRATION.md
@@ -540,6 +540,4 @@ The `camel-report-maven-plugin` has the `validate` and `route-coverage` goals wh
 
 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.
 
-The tracer feature does not work (the implementation from Camel 2.x was deprecated), and we plan to implement a new and improved tracer.
-